-
Notifications
You must be signed in to change notification settings - Fork 17
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
Are glob/regex supported? #48
Comments
Thanks for opening this issue. Currently, there is no support for globbing in We are struggling a bit with your request. On one hand, we certainly acknowledge that such a feature could be useful. On the other hand, we appreciate explicitness when dealing with secrets. Maybe we could strike a balance by introducing an additional flag {
"hosts/host1/*" = {
publicKeys = [ system1 ];
glob = true;
};
} Would that work for you? |
Of course, that would be great! If a secret is matched by multiple globs, the rules would be merged I suppose? |
I think #52 (with |
You can just use |
I'm wondering how to organise my secrets without specifying every single one of them explicitly
Is there some mechanism of how to specify glob patterns or regex's in the
secrets.nix
file?It would be nice to be able to specify something like this:
In this example every host should be able to access anything in his directory and the backup-admin should additionally be able to access the backup-keys for all hosts (but not the other files of all hosts).
Is this possible?
The text was updated successfully, but these errors were encountered: