Skip to content
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

Make all secrets settable via files #106

Closed
hairyhenderson opened this issue Mar 12, 2017 · 0 comments
Closed

Make all secrets settable via files #106

hairyhenderson opened this issue Mar 12, 2017 · 0 comments

Comments

@hairyhenderson
Copy link
Owner

With new Docker Swarm Secrets, and when running gomplate inside a container running in a Swarm service, it'd be more secure for gomplate to be able to read secrets from files instead of environment variables. See https://docs.docker.com/engine/swarm/secrets/#build-support-for-docker-secrets-into-your-images

I'm thinking of pretty much everything passed through an environment variable, but especially:

  • VAULT_APP_ID
  • VAULT_USER_ID
  • VAULT_AUTH_GITHUB_TOKEN
  • VAULT_AUTH_USERNAME
  • VAULT_AUTH_PASSWORD
  • VAULT_ROLE_ID
  • VAULT_SECRET_ID
  • VAULT_TOKEN - even though ~/.vault-token is already read by default, this one is still valuable since swarm secrets can only be exposed at /run/secrets (because they're in a tmpfs in-memory filesystem)

Basically each one of these would have an equivalent *_FILE version that would point to a file to be read.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant