Client Example for Managed Secrets - Relies on:
-
vault configured by https://github.com/nikogura/keymaster-cli
This repo is a reference implementation of a client for the public libraries listed above.
Designed to be run from dbt https://github.com/nikogura/dbt, but can also be run as a bare binary.
For usage with dbt run the following to get subcommands and options: (assuming you have dbt set up in your organization of course)
dbt secrets help
-
Fetch the version of your choice from wherever you keep the binanaries.
-
Run with:
./secrets help
As configured, this tool will attempt to authenticate you via LDAP if it cannot do so any other way.
On a laptop this is cool, but when used in an automated fashion it's probably not what you want. Specify 'silent' mode by adding the -s flag:
[dbt] secrets <verb> -s
From an EC2 machine, run:
[dbt] secrets fetch -r <team>-<role>
From within a pod in the appropriate Namespace in K8s, run:
[dbt] secrets fetch -i <cluster> -r <team>-<role>
From a machine possessing a certificate signed by your root CA, run:
[dbt] secrets fetch -r <team>-<role>-<environment>
From any machine that can connect to the LDAP server, run:
[dbt] secrets fetch -r <team>-<role> -e <environment>
Append -k <key>
Append -k <key> -f raw
Append -k <key>
Append -k <key> -f raw
This example is for k8s. Other realms are similar to fetch syntax, above
[dbt] secrets exec -i <cluster name> -r <team>-<role> '<program to exec>'
Your secrets will appear in ENV to be consumed by the program you have supplied as the final argument to the command.
The secrets tool will attempt to authenticate you via your personal LDAP credentials if it cannot do so via k8s, tls, or iam. In an interactive shell during development, this can be useful, but when used in an automated fashion, it will cause your script to hang (or exit), waiting for an LDAP password that will never arrive. You can turn off the LDAP auth attempt in a script with the 'silent' switch:
[dbt] secrets <verb> -s
which can be combined with the -r or -i switches for tls and k8s realm types, respectively:
[dbt] secrets exec -sr <team>-<role>-<environment> '<program to exec>'
If [dbt] secrets fetch ... or [dbt] secrets exec ... fail to delight you, try running again with the -v flag (verbose).
It will dump a very large amount of information regarding what it's connecting to, and how it's trying to auth, and the like. Happy Hacking!