Sender | Message | Time |
---|---|---|
5 Dec 2022 | ||
In reply to @ryantm:matrix.orgThis is my flake.nix https://0x0.st/ok0G.nix | 02:31:48 | |
I can share one of the hosts too | 02:32:02 | |
It would help to see all the lines for agenix at least. | 02:33:00 | |
aaa/host.nix https://0x0.st/ok0n.nix | 02:33:51 | |
And configuration in a sec | 02:34:02 | |
https://0x0.st/ok07.nix | 02:36:23 | |
That's all the agenix stuff, except for secrets/secrets.nix | 02:38:00 | |
Looks pretty good. | 02:38:09 | |
I don't typically use path + string for the file config so it would be a debugging step to write the real path out there. | 02:38:51 | |
Also double check you've staged the secrets into your flake repo. | 02:39:38 | |
In reply to @ryantm:matrix.orgAh that is likely it. I have only an inkling that the repo contents affect things | 02:40:44 | |
secrets dir explicitly left out of repo in .gitignore | 02:40:59 | |
Yeah. Seems to be working now. | 02:43:06 | |
So I really ha e no choice but to commit secrets to my repo? | 02:43:35 | |
* So I really have no choice but to commit secrets to my repo? | 02:43:42 | |
6 Dec 2022 | ||
03:18:07 | ||
7 Dec 2022 | ||
04:30:50 | ||
9 Dec 2022 | ||
05:22:21 | ||
regarding the template discussion: current agenix decrypts the secret and writes it to disk. if someone needs post processing (transforming the secret, combining it with other config) one can use the `system.activationScripts` to read said secret and write it to another file, but needs to make sure it has the correct permissions and it's not committed to the nix store by accident. | 12:46:47 | |
there is currently a pull request, that would introduce templates, so one could specify a template with `@secret1@` template variables, and those would be replaced by the secrets, and handle the permissions. | 12:48:56 | |
have you thought about adding a more general "transform" attribute for each secret? you could specify a script there. agenix would then write the secret to the stdin of said script and write the scripts stdout to the file. this way also more complex transformations would be possible. perhaps agenix could even provide a default implementation of said script: the secret could be a toml/ini/json/yaml file that defines the variables, a command line argument of the script could point to a template. the default could be a simple `cat` that does not transform anything. | 12:53:30 | |
I'd love to see something like this in agenix. I spent many hours getting templates working for myself, it definitely feels like advanced nix, and is a roadblock to adopting flake based nix deployments. | 17:30:01 | |
11 Dec 2022 | ||
08:11:08 | ||
Hi! First wanna say thanks for happy years using agenix ^^ I just upgraded a NixOS host to 22.11 and in so doing updated the agenix flake input from rev. For example, with the following configuration (unchanged for several NixOS releases):
a rebuild generates the following output:
and a listing of the resulting secrets directory is as follows:
Since I haven't updated this host in a while, maybe there's a setting I missed? Thanks! | 09:20:09 | |
acire: glad you've been happy with agenix up to this point! Do you want code that is doing anything with activation scripts in your config? | 12:51:17 | |
* acire: glad you've been happy with agenix up to this point! Do you have any code that is doing anything with activation scripts in your config? | 12:51:40 | |
Can you show the dir listing for the /run/agenix.d/1 folder too? | 12:54:47 | |
Are you doing anything in your config with config.age.secretsDir? | 12:56:45 | |
ryantm: thanks for your reply!
| 13:42:36 | |
Redacted or Malformed Event | 15:40:39 |