Suggestion: Don't create final DB snapshot when destroying Amazon RDS instance #243
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.
While using viya4-iac-aws to provision an Amazon RDS instance, I noticed that a database snapshot is created when doing a 'terraform destroy'. The user doesn't really have any way to know that this snapshot is created, and it will persist indefinitely until the user manual deletes it. Personally, when doing a 'terraform destroy', I would expect all resources to be removed, or at least some indication that something is being left behind.
It looks like the rds module provides a skip_final_snapshot flag which can be used to control this behavior. This PR simply sets this flag to true by default rather than false.