Secrets

Thanks to Outblocks you can manage your secrets in a team-friendly way. Secrets are per environment and per project. Secrets can be used the same way as environment variables. e.g. ${secrets.secret_name}.

Note: GCP plugin supports secrets out of the box. If multiple plugins support secrets, one can select which one will be used. Still, it’s not needed for now as only one secret plugin is available.

Managing secrets

You can manage secrets using CLI:

ok secrets

You can use those commands:

• delete - delete secret
• get - get one
• set - set one value
• view - view all secrets
• import - import from file
• edit - load current secrets and open them in $EDITOR (defaults to vim/nano/vi)

Examples:

Setting new secret:

# ok secrets set [flags] <key> <value>
# by default set for 'dev' environment
ok secrets set API_KEY <your secret key>

Setting new secret - production environment:

ok secrets set --env=production API_KEY <your secret key>