Add args option for age key generation#942
Open
LucasWagler wants to merge 4 commits intoMic92:masterfrom
Open
Conversation
6139ced to
da91d27
Compare
LucasWagler
commented
Apr 10, 2026
da91d27 to
e1b7f5b
Compare
e1b7f5b to
46255b9
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add a flexible
sops.age.extraGenerateKeyArgsoption to the base/NixOS, home-manager, and darwin modules.This enables:
age-keygencurrently offers option-pqfor this. This is the primary driver behind the PR.age-keygenadds more options in the future,sops-nixusers can use this escape hatch without waiting for new development.💬 Seeking Feedback: Option Naming
Here are some options I'm considering:
generateKeytokeyGeneration.enable& addkeyGeneration.extraArgskeyFileoption is left out, despite also being relevant.keyFileimpacts key generation, but also has a purpose outside of generation.extraGenerateKeyArgsI like the first option better, but the second option is what is currently implemented. Let me know your thoughts!