fix: min retention days and max retention days required #96
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.
This pull request includes several changes to improve the validation and documentation of the AWS backup module. The most important changes include updating the validation logic for vault retention days, updating the AWS provider version, and documenting these changes in the changelog.
Validation improvements:
main.tf
: Updated the precondition logic in theaws_backup_vault
resource to ensuremin_retention_days
andmax_retention_days
are provided when vault locking is enabled and to validate thatmin_retention_days
is less than or equal tomax_retention_days
. It fixes Variables min_retention_days and max_retention_days required after 0.23.0 #95Documentation updates:
CHANGELOG.md
: Added a new entry for version 0.23.3, documenting the fixes for vault retention days validation and conditions in backup selections.README.md
: Updated the AWS provider version from 5.89.0 to 5.91.0.