-
Notifications
You must be signed in to change notification settings - Fork 547
feat(aws)!: Define composite primary key for lambda_function_versions #12402
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(aws)!: Define composite primary key for lambda_function_versions #12402
Conversation
This PR has the following changes to source plugin(s) tables:
|
erezrokah
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great @smokentar 🚀 I added another commit to fix the styling and make the CI happy
|
Thanks for the PR @smokentar, see the expected release version in #12406. |
🤖 I have created a release *beep* *boop* --- ## [22.0.0](plugins-source-aws-v21.1.0...plugins-source-aws-v22.0.0) (2023-07-20) ### ⚠ BREAKING CHANGES * **aws:** Define composite primary key for regions ([#12415](#12415)) * **aws:** Define primary key for s3_bucket_encryption_rules ([#12408](#12408)) * **aws:** Define primary key for dynamodb_table_continuous_backups ([#12409](#12409)) * **aws:** Define composite primary key for lambda_function_versions ([#12402](#12402)) ### This Release has the Following Changes to Tables - Table `aws_appconfig_deployment_strategies` was added - Table `aws_dynamodb_table_continuous_backups`: primary key constraint added to column `table_arn` (:warning: breaking) - Table `aws_dynamodb_table_continuous_backups`: primary key constraint removed from column `_cq_id` (:warning: breaking) - Table `aws_lambda_function_versions`: primary key constraint added to column `function_arn` (:warning: breaking) - Table `aws_lambda_function_versions`: primary key constraint added to column `version` (:warning: breaking) - Table `aws_lambda_function_versions`: primary key constraint removed from column `_cq_id` (:warning: breaking) - Table `aws_regions`: primary key constraint added to column `account_id` (:warning: breaking) - Table `aws_regions`: primary key constraint added to column `region` (:warning: breaking) - Table `aws_regions`: primary key constraint removed from column `_cq_id` (:warning: breaking) - Table `aws_s3_bucket_encryption_rules`: primary key constraint added to column `bucket_arn` (:warning: breaking) - Table `aws_s3_bucket_encryption_rules`: primary key constraint removed from column `_cq_id` (:warning: breaking) ### Features * **aws:** Define composite primary key for lambda_function_versions ([#12402](#12402)) ([d1add18](d1add18)) * **aws:** Define composite primary key for regions ([#12415](#12415)) ([681ea97](681ea97)) * **aws:** Define primary key for dynamodb_table_continuous_backups ([#12409](#12409)) ([7d4a657](7d4a657)) * **aws:** Define primary key for s3_bucket_encryption_rules ([#12408](#12408)) ([a026b98](a026b98)) ### Bug Fixes * **sync:** Pass `DeterministicCQID` option to scheduler ([#12424](#12424)) ([eaac2e6](eaac2e6)) * Use correct name for `DeploymentStrategies` table ([#12428](#12428)) ([dda4205](dda4205)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
Summary
This PR is aimed to address #12391 by creating a composite primary key on
aws_lambda_function_versionstable comprisingfunction_arnandversion.Since
function_arnwill always be unique,account_idorregionare not required to be part of the primary key.Summary
This is my first PR against the codebase, extra pair of eyes are highly recommended!