feat: Add in overwrite variable and pass through to the call to the ssm par… #11
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.
…ameter resource that is not ignoring value changes
Description
For context, I added an issue as well: #10
Adding in support for passing through the
overwriteattribute of theaws_ssm_parameterresource: https://registry.terraform.io/providers/hashicorp/aws/6.17.0/docs/resources/ssm_parameter#overwrite-14Motivation and Context
The
overwriteattribute on theaws_ssm_parameterseems to remain as a non-deprecated attribute, so ensuring that this piece of the SSM parameter functionality can be utilized via this module.Breaking Changes
Assuming there aren't any actual versions of the AWS provider/AWS APIs where this was indeed removed from support from AWS apis, then I think it wouldn't be breaking?
How Has This Been Tested?
I can go through some testing scenarios/add test cases if this is even the right move. Figured I'd start here w/ just proposing it basically and I will move forward w/ that if this looks like the right move.
examples/*to demonstrate and validate my change(s)examples/*projectspre-commit run -aon my pull request