FEATURE CE-454: Set Config retention via native TF #11
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kristian-lesko
force-pushed
the
feature/CE-454_config_retention
branch
2 times, most recently
from
309bc7b
to
d686ef1
Compare
kristian-lesko
force-pushed
the
feature/CE-454_config_retention
branch
from
d686ef1
to
15d366d
Compare
marko-fabry
approved these changes
Mar 1, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Thanks to hashicorp/terraform-provider-aws#27262 (and previously #9), we no longer need a custom Python local provisioner to configure AWS Config retention and frequency. We can set these attributes via native Terraform from now on.