feature: added support for substituting secrets into files #290
Conversation
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
elliott-farrall
force-pushed
the
main
branch
from
6f3ecb9 to
f2725cd
Compare
elliott-farrall
force-pushed
the
main
branch
11 times, most recently
from
c001142 to
9d8b935
Compare
elliott-farrall
force-pushed
the
main
branch
7 times, most recently
from
c9831d6 to
138bde8
Compare
elliott-farrall
force-pushed
the
main
branch
from
138bde8 to
355c932
Compare
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.
A while ago I started using agenix with an additional feature to allow the substitution of decrypted secrets into files and it was recently suggested that I look into upstreaming this feature.
The core functionality (that is added to both the nixos and home-manager modules) is implemented via the
age.secrets.secret-name.substitutionsoption. When given a list of file paths (as strings), any instance of@secret-name@in these files will be substituted with the corresponding secret. If the file is managed viahome.filein home-manager, I recommend settingforce = truefor this file to avoid collision warnings.I haven't implemented any additional tests for this feature yet but can look into it if needed.