Closed isuftin closed 8 years ago
Thanks for your suggestion!
I think we would prefer to keep this kind of logic in wrapper cookbooks. There are several ways to store "secrets" and to hide them, we don't want to impose one solution.
For reference, we are using chef-vault to store secrets and use chef-secret to "hide" attributes set by wrapper cookbook. See https://github.com/criteo-cookbooks/chef-secrets for details.
I think you can set data from encrypted databags (as chef-vault) into the attributes and hide them with chef-secret. Then your solution is very close to ours.
I've created a wrapper cookbook that allows me to place sensitive information into encrypted data bags instead of into node attributes visible to anyone.
The wrapper cookbook looks something like this:
I wonder if you would find it useful for me to bring in something like this as a PR to your cookbook or did you want to keep yours as is and delegate this functionality to upstream wrapper cookbooks?