-
Notifications
You must be signed in to change notification settings - Fork 155
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expose the values of unencrypted keys as-is #317
Comments
I could read |
I would accept this as a contribution but won't implement it as I don't have a use-case for it. |
This comment was marked as resolved.
This comment was marked as resolved.
sops-nix can only support formats also supported by sops. It relies on sops for editing secrets and it's unlikely that they will add nix. There is not import-from-derivation required to check yaml. It's just a normal nix derivation. |
Closing, because I no longer need this, as I'll just use JSON as the secrets format (though, that requires #328). |
A subset of keys in
secrets.yaml
can be marked as unencrypted by suffixing them with_unencryprted
. This is useful for things like SSH public (not private) keys.Can sops-nix expose these unencrypted values during evaluation? Not as
.path
(which points to/run/...
path, accessible only during runtime), but as.text
(accessible during evaluation time)?I could then store public keys in secrets.yaml (along with the encrypted private keys) and use them to set options like
users.user.<name>.authorizedKeys
in a say container (that has no access to the host's/run
directory).The text was updated successfully, but these errors were encountered: