Adding deployment.keyDirs
option to recursively deploy directories of keys
#632
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.
Instead of having to manually specify each key to deploy, recursively copy the contents of a local directory under /run/keys.
This is particularly helpful when deploying servers having multiple user accounts that need nixops. Each user would have his own key folder, owned by him that he can use for his deployments. Otherwise, using
deployment.keys
, one line per key is needed.deployment.keyDirs
supports having different permissions on directories than files inside them. Key directories will be deployed uponnixops deploy
ornixops send-keys
only ifdeployment.storeKeysOnMachine
is set to false.Also changed
nixops-keys
systemd unit's script to account for whendeployment.keys
ordeployment.keyDirs
is empty.