feat!: remove GuSsmParameter #1157
Merged
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
See: #1032 This construct is unused and better alternatives exist.
2 tasks
akash1810
approved these changes
Mar 11, 2022
|
🎉 This PR is included in version 38.1.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
What does this change?
GuSSMParameteris a custom resource that allows using SSM parameters within Cloudformation templates.It is quite complex and is (as best we know) unused. See: #1032 for a wider discussion.
The new preferred approach is simply to either:
How to test
n/a
How can we measure success?
(Reduced complexity and smaller codebase.)
Have we considered potential risks?
(Breaking change for anyone using this.)
Checklist
(I don't think we need to make documentation changes here.)