Recursively get parameters from SSM #1
Merged
Conversation
This file contains hidden or 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
getParametersByPath calls itself again if the NextToken output tells us there are more params to be fetched
Owner
|
Thank you! I'll release this update in about a week. |
Contributor
Author
|
Much appreciated @rkit ! |
Contributor
Author
|
Hey @rkit, wanted to check in again and see if you know when you'll have time to check this out for us? |
Owner
|
Done. Thank you 👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Once I added an 11th param to our param store in SSM, I noticed we were only getting 10 results back. The AWS SDK docs revealed that we could set the max number of results to increase the results or take advantage of the
NextTokenI updated the code so that
getParametersByPathcalls itself again if theNextTokenoutput tells us there are more params to be fetched.