Update Terraform cloudposse/sns-topic/aws to v0.15.0 #8
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 PR contains the following updates:
0.9.0
->0.15.0
Release Notes
cloudposse/terraform-aws-sns-topic
v0.15.0
Compare Source
context.tf updated to v0.24.1, minimum required Terraform version bumped to 0.13.0 when needed, readme updated @maximmi (#30)
#### what - update context.tf to v0.24.1 - minimum required Terraform version bumped to 0.13.0 - readme updated, Bridgecrew compliance badges added #### why - It allows for setting the letter case of tag names and labels, back compatibility with context v0.22.0 and below - we have dropped support for Terraform 0.12 - To be able see and fix the recommendations from Bridgecrew so we can position our modules as standards compliantv0.14.0
Compare Source
minimum required Terraform version bumped to 0.13.0, context.tf updated, readme updated @maximmi (#29)
#### what - update context.tf to v0.23.0 - minimum required Terraform version bumped to 0.13.0 - readme updated, Bridgecrew compliance badges added #### why - It allows for setting the letter case of tag names and labels - we have dropped support for Terraform 0.12 - To be able see and fix the recommendations from Bridgecrew so we can position our modules as standards compliantv0.13.0
Compare Source
readme updated, BC conpliance checks fixed @maximmi (#26)
#### what * BridgeCrew compliance checks fix * readme updated * default behaviour changed: `Encrypt SNS Topic Data` enabled by default * default behaviour changed: `Encrypt SQS Queue Data` enabled by default #### why * To be able to position our modules as standards compliant * Providing explicit note about policy attached directly to user * To comply BridgeCrew check #### references * https://docs.bridgecrew.io/docs/general_15 * https://docs.bridgecrew.io/docs/general_16-encrypt-sqs-queuev0.12.0
Compare Source
Terraform 0.14 upgrade @maximmi (#24)
#### what - Upgrade to support Terraform 0.14 and bring up to current Cloud Posse standard #### why - Support Terraform 0.14v0.11.0
Compare Source
v0.10.0
Compare Source
what
why
NOTE: The value defaults to null, which instucts terraform to use the default retry policy. I've tested this for both scenarios (Returning back to a default policy, and ensuring the default policy is still used if the var is not supplied).
Renovate configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻️ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by WhiteSource Renovate. View repository job log here.