You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The names RULES and secrets.nix are very generic and unrelated to agenix, to the point that any conscientious programmer can't avoid adding comments like "this variable holds the path to the agenix rules file" or "this is the agenix rules file" (ok, maybe only OCD programmers are affected).
Could you switch to something like AGENIX_RULES and agenix-rules.nix in a future version? (maintaining backwards-compatibility, of course).
The text was updated successfully, but these errors were encountered:
BTW: I don't have much experience with either go or nix, but this seems easy enough that I can do it if you are willing to accept a PR (and would rather not do it yourself, of course)
BTW (since I'm here I'm not opening a separate issue), a second environment variable for holding what ssh key to use (as per the -i option) would be great... since my id_ed25519 is passphrase-protected I generated a key for agenix, but now I have to specify -i ~/.ssh/agenix_ed25519 every time
The names
RULES
andsecrets.nix
are very generic and unrelated to agenix, to the point that any conscientious programmer can't avoid adding comments like "this variable holds the path to the agenix rules file" or "this is the agenix rules file" (ok, maybe only OCD programmers are affected).Could you switch to something like
AGENIX_RULES
andagenix-rules.nix
in a future version? (maintaining backwards-compatibility, of course).The text was updated successfully, but these errors were encountered: