parameter-store-manager
parameter-store-manager copied to clipboard
Generalize service parameter creation
Currently there are two flows when it comes to parameter creation: services and generic.
services is just a faster way to create many parameters across different environments at once.
services assumes the path convention that I use which is /services/{env}/{serviceName}/{parameterName}.
Other teams may do this differently, so make the ability to either template-fy services parameters or support other people's use cases.
I am very keen to see more examples of usable path conventions etc.
And another ....
feature request
Please expose configuration for Environments
Or at least more generic:
- local
- dev
- test
- staging
- prod
- common