Manage the organization's credential vault.
A secret stored here is injected into the sandbox's outbound requests by the
egress proxy, on the host, after the sandbox has handed the request over. The
sandbox cannot read it, and neither can this CLI: no response on any vault route
carries a value, so there is no "get" command.
A secret records the hosts it may be sent to. That list is not a convenience --
without it, anyone who can write an egress rule could aim your credential at a
server they control and read it out of their own access log. A secret with no
list cannot be used at all.
To use a secret, name it in a sandbox's network rules:
anona-compute vault create gh_token --host api.github.com --value-file token.txt
anona-compute create --no-internet \
--allow-out api.github.com \
--vault-inject api.github.com:Authorization=bearer:gh_token
A rule injects into requests to its host; it does not open that host. With
--no-internet, name the host in --allow-out too, or the request is refused.
Creating a new binding needs an owner or admin login, or an API key with the
vault:bind scope. That scope is in no preset, including full_access: it has to
be chosen deliberately when the key is made.
Usage
anona-compute vault [flags]
anona-compute vault [command]
Commands
| Command | Description |
|---|---|
vault allowed-hosts | Replace the hosts a secret may be sent to |
vault create | Store a new secret |
vault delete | Delete a secret and every binding of it |
vault list | List secrets, their allowed hosts and their bindings |
vault rotate | Store a new version of a secret and make it current |
vault unbind | Revoke one binding, leaving the secret |
Flags
| Flag | Type | Description |
|---|---|---|
--help, -h | help for vault |
--api-key, --api-url, --json, --output, --profile, --request-timeout, --verbose) work on every command; see anona-compute.