Add symlink to secrets
More flexibility and less dots in config files.
Implements #65 (closed).
Merge request reports
Activity
11 11 then import path 12 12 else default 13 13 ); 14 sshUsers = importDef {} ../../../../PrivateStorageSecrets/staging-users.nix; -
I still don't understand why we had four levels of dir traversal here and only two in
config.jsonand it nevertheless worked.This MR does away with that - please double check I understood you right @jcalderone :)
Edited by Florian Sesser Yea I'm not exactly sure why different grids thought Secrets was a different distance away. I have some vague idea about how these paths were getting evaluated relative to the morph working directory (plus inconsistency in what directory I ran morph from) but I'm not really confident in this explanation ... I think nix paths are relative to the source file they appear in (though that wouldn't matter for the paths in
config.jsonsince those are just strings, not nix paths). Happy to avoid this issue in the future with the secrets symlink.
42 42 43 43 Specific grid definitions live in subdirectories beneath this directory. 44 44 45 secrets 46 ~~~~~~~ 47 48 This must be created and populated before the grid can be built or deployed. 49 50 This directory contains all of the secrets necessary to deploy the grid. 51 Secrets beneath this directory are referenced by ``config.json`` and ``grid.nix`` 52 (and possibly elsewhere). 53 Some of the paths are configurable and some are just convention. 54 This path is **ignored** by git. mentioned in commit 13d8f91d
