-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support Global ParameterStore path for all stages #299
Comments
Neat, I could see that being a useful feature. To clarify, |
Ahh great question. So I wanted to support both exact and recursive. So lets say take NewRelic for example. They have 4-6 different keys. Lets take the 4 most common ones.
Let say in parameter store you have those values stored like so
I would like to support both these scenarios Exact
Recursive
|
I wanted to expose |
Can you clarify what you mean by exposing the naming function, and how that might work with this new feature? |
So ParameterStoreWrapper has a bunch of options so I'm thinking we support
We can pass an array of options as a second argument |
So instead of duplicating certain values for each environment stage example NewRelic, Datadog, Pagerduty api keys. It might be beneficial to add a Global ParameterStore option when the plugin is initiated.
Example
The text was updated successfully, but these errors were encountered: