fix appconfig configuration version drift on each run #44847
+130
−1
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.
Description
Fixes persistent drift detection in aws_appconfig_hosted_configuration_version when using AppConfig feature flags. AWS AppConfig automatically injects _createdAt and _updatedAt timestamp metadata fields into feature flag configurations at the
flags.*andvalues.*levels, which are not present in the Terraform configuration. This causes Terraform to incorrectly detect drift on every plan/apply cycle, even when no actual changes have been made.Example Drift Scenario (Before Fix)
After initial apply, subsequent terraform plan would show drift due to AWS adding:
Relations
n/a
References
n/a
Output from Acceptance Testing