secrets management about vaultconf HOT 4 CLOSED

One tool to rule them all? Not sure that works in practice well.

from vaultconf.

I get wanting vault AWS policies managed in the same tool, think that makes sense, given we are managing vault policies with it. Not sure what you mean by secrets though? Surely we don't want our secrets in github? The point of vault is to securely house our secrets.

from vaultconf.

So by secrets, example ... i mount aws backend and i push 12 aws iam policies giving access to this, (ses, s3, etc etc) that and the other ... then some bastard comes along and destroys my vault and i have to remember this policies and import them back into ... but if i have them in a repo somewhere ... vaultconf secrets -c filename

from vaultconf.

Yep still agree for aws iam policies!

By secrets I thought you meant you wanted stuff like credentials in github

from vaultconf.