chamber: chamber secure --resecure no longer works
Current Behavior
chamber secure --resecure is described on this page of the docs, linked from this page on re-securing. It seems like a helpful feature for my use case - rotating the keys used to encrypt the config. There are two main use cases for this: security policy mandates rotating keys, and a leak of the key.
Steps to Reproduce
- Run
chamber secure --resecureon the command line - Receive
ERROR: "chamber secure" was called with arguments ["--resecure"]
The option appears not to exist in the task description file, which would explain why it doesn’t work.
Screenshot
Expected Behavior
Chamber should give you the option to recreate the keys. The docs aren’t actually clear on what should happen, actually. At the very least, the docs should be updated to match the gem’s functionality.
Environment
- Device: 2021 MacBook Pro
- OS: macOS
- OS Version: Monterey
- Running Ruby via asdf
- Other commands with Chamber CLI works
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 15 (5 by maintainers)
@ideasasylum I agree that as a “go small” simply adding a command to decrypt all values may be good enough since you can just re-run
chamber secure.3.1 has been released with
unsecure! 🎉I’ve removed
resecurefrom the wiki and added a stub forunsecurefor now. I’ll close this in favor of #79Thanks everyone!
@ideasasylum I’m updating wikis and finalizing everything for a 3.0 final release in the next day or two. I will release 3.0 with all the deprecations removed and then almost immediately release a 3.1 with your “unsecure” command.
Thank you all for the patience. I’m only one person and don’t have a ton of time to work on this stuff throughout the year.
@UsAndRufus @ideasasylum I have time blocked out in December for this. I haven’t forgotten about this or #79
This is actually what I’m doing now to restrict the blast radius the next time this happens
Hey all! This has been on my list for quite a while but I think I’ll actually get finished with it this year at some point. Give me a couple more months and we’ll see where we are. I would suggest making sure you’re upgraded to the latest Chamber 2.x version which will give you deprecations since this feature will only be implemented on the 3.x branch.
The primary change has been to consolidate all lookups to a single public method rather than having to do massive amounts of metaprogramming (and relying on
hashie) to do the plethora of lookups that Chamber 2.x did.To follow up: I did take a stab at this and I think I have something working but I can’t get the test suite to pass locally, even on
master. Perhaps I’m missing a key or something @jfelchner?These are the failing specs for me:
all with errors like