docs: Add example for dealing with compromised key#34
Conversation
The order of operations in this scenario is very specific and error-prone. It would make sense to document this right here in this project. Signed-off-by: fhoekstra <32362869+fhoekstra@users.noreply.github.com>
✅ Deploy Preview for getsops ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Signed-off-by: fhoekstra <32362869+fhoekstra@users.noreply.github.com>
felixfontein
left a comment
There was a problem hiding this comment.
Thanks for your contribution! I think it is a great idea to have a section on this in the docs. I've added two comments below, which are my personal ones; maybe someone else from @getsops/maintainers might want to comment on them?
Also note that currently there's a large reorganization happening (#31) which conflicts with tihs PR (and in fact with any other PR changing the documentation). I don't know how long it will take @getsops/maintainers to review that PR, so whether it makes sense to merge this one first and rebase the other, or the other way around.
Co-authored-by: Felix Fontein <felix@fontein.de> Signed-off-by: fhoekstra <32362869+fhoekstra@users.noreply.github.com>
I am interested in this subject right now because of the move to post-quantum encryption. Currently waiting for FluxCD 2.9 to be released, and then a lot of Kubernetes users of SOPS will be looking at moving to post-quantum. I'm looking to do a simple how-to blog post on it either way, it would be nice if I could point at the official documentation for this process. But I understand there's "always something" and I wouldn't want to slow down the docs improvement project. |
|
Also would you mind changing the commit message above to remove the |
…s and clarify checking in of the updated file. Signed-off-by: fhoekstra <32362869+fhoekstra@users.noreply.github.com>
Signed-off-by: fhoekstra <32362869+fhoekstra@users.noreply.github.com>
Co-authored-by: Felix Fontein <felix@fontein.de> Signed-off-by: fhoekstra <32362869+fhoekstra@users.noreply.github.com>
|
Ah sorry, I keep forgetting about Github's enthusiastic notification policy 😅 |
The order of operations in this scenario is very specific and error-prone. It would make sense to document this right here in this project.
I would appreciate any feedback and/or corrections!