Skip to main content

Connection flags

Every network command takes these three. They pick where the command talks and as whom; the output forms pick how the answer renders.

FlagTypeDefaultWhat it does
--context <name>stringthe config's currentuse this named context for one call
--config <path>string$GRAPHENE_CONFIG, else ~/.config/graphene/config.yamlread contexts from this file
-n, --namespace <ns>stringthe context's namespacenamespace for one call — meaningful for cluster-wide admin tokens (*); a namespaced token is pinned to its own scope by the server

Examples

One call against another installation without switching:

$ graphenectl get run --context prod

A CI job with its own config file:

$ graphenectl run list --config ./ci/graphene.yaml

An admin token surveying another namespace:

$ graphenectl get all -n team-b

The full resolution chain — file, context, environment overrides — is described in Contexts.