ssm-diff
ssm-diff copied to clipboard
runtheops
A human-friendly way of managing parameters in AWS SSM
Handling parameters description would be a nice touch, maybe via YAML comments. What do you think ?
This PR is built on #18 (for easy merging) but is mostly unrelated. It introduces a variety of improvements to the storage engines (i.e. `YAMLFile` and `ParamterStore`) with related changes...
A final suggestion is to change the top-level package name to something that's more meaningful (e.g. `ssm_diff`). A programmatic user currently imports from `states` which isn't necessarily obvious. The diff...
This PR builds on `refactor`, adding a plugin system for `Diff*` engines. To make the plugin system work, I needed to simplify the interface between `ParameterStore` (formerly `RemoteState`) and `DiffResolver`...
Before submitting PRs to add new behaviors, I wanted to wrap my head around the current codebase. I started with some basic contributor-friendly changes: - add documentation - clarify variable...
I've been digging through the implementation and it looks like the `force` flag in `pull` only supports two modes: - Keep all local value and add any new values from...
I think the commands would be more intuitive if they mirrored git/docker e.g. (edit: add/tweaked mappings): - init = clone (or fetch) - pull = pull - plan = status...
It seems to me that the following will result in the deletion of **many** keys: - `ssm-diff init -p "a/b/c"` - `ssm-diff plan -p "a/b/c"` - `ssm-diff apply` It would...
Any thoughts on adding a root path configuration? For example, I may only want to extract `/Prod/Service//` to a YAML for revision and then push it back up. We've been...
Unless absolutely necessary, I'd rather not put decrypted secrets on a local machine. SSM also logs access to secrets so I'd rather not leave an unnecessary trail of secrets logs....