sops shouldn't lose edits when KMS access is denied
yeah, let's do that :)
What behavior would we want here? Is showing an error message and asking the user to decide whether to be put back in their editor or to exit acceptable? That's the same thing we do when the YAML/JSON syntax is invalid, or when no master keys are provided.
Yes, I think that is sufficient.
I'd like to work on this if no one else is working on it.
I think this has been fixed for a while, but if you want to verify it and fix it if it's not fixed, go right ahead.
@autrilla how can I cause this access denied message?
Revoke permissions to a KMS key after opening the editor
I'm interested in working on this issue. Could you provide more context about what you're looking for? Any additional details about requirements or constraints would be helpful.