Add tags to blue green deployment creation #45078
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Rollback Plan
If a change needs to be reverted, we will publish an updated version of the library.
Changes to Security Controls
Are there any changes to security controls (access controls, encryption, logging) in this pull request? If so, explain.
No changes.
Description
This fixes a bug where the blue green deployment did not have any tags attached to it since it wasn't set when creating the deployment.
In cases where IAM rights are based on resource tags this results in blue green deployments not working with the terraform provider.
Relations
None
References
Output from Acceptance Testing
I currently ran a single test
TestAccRDSInstance_BlueGreenDeployment_updateEngineVersion, which I changedto ensure the defaults tags from the provider where used.
I inspected the RDS blue green deployment in the AWS console, since I don't know how I can automate this in a test, since after terraform apply the blue green deployment resource is gone