-
Notifications
You must be signed in to change notification settings - Fork 404
feat(aws-ssm): Support parameters by path #603
feat(aws-ssm): Support parameters by path #603
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't know the code conventions in this repo so I only skimmed through this PR and added some small suggestions.
Thanks for re-working the PR! I am looking forward to seeing this shipped :) It's going to simplify our setup a lot.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for updating this! I like this new approach better of reusing the same backend type and data
structure.
Would love to see some tests covering this as well!
d1a17a9
to
7695bca
Compare
Updating Readme Improving code with users suggestions Lint fixes Adding tests for ssm path feature
7695bca
to
49abbd3
Compare
@Flydiverny created one test for this new feature. Let me know if it's enough :) |
@rjmsilveira I'm trying to get us off our fork where we use data by path, but seems like I cannot use this approach as I get the following error Why would those be required when the only path is used? |
I forgot to update CRD, all good now! |
This MR is a replacement of my original approach (#238 )
I have refactored the code to do have as little changes as possible but still supporting the possibility of fetching secrets from a path instead of a key.
Also added support to fetch paths recursively if needed but the default is 0.