dexaflow target

Manage named control planes (targets) to deploy to and query.

Synopsis

A target names a control plane. Inside a workspace, targets are kept in dexaflow.workspace.yaml and shared with everyone who clones it; outside a workspace, or with –global, they are kept in your config file.

Every server command takes –target . The server a command calls is: –server or –server-url; then –target, then DEXAFLOW_TARGET; then DEXAFLOW_SERVER_URL; then the target chosen with dexaflow target use for this workspace, the workspace’s default_target, or current_target from the config file; then server_url from the config file.

Tokens are never stored in the workspace file: dexaflow auth login --target <name> saves one per server in your config file.

Options

  -h, --help   help for target

Options inherited from parent commands

      --config string       config file path (default ~/.dexaflow/config.yaml)
      --log-level string    log level: debug, info, warn, error
      --server-url string   control plane API base URL
      --target name         name of the control plane to use (default: DEXAFLOW_TARGET, then the target selected for the workspace; see dexaflow target list)

SEE ALSO

• dexaflow - Dexaflow is a GitOps-first, container-native workflow orchestrator.
• dexaflow target add - Add a target (to the workspace file, or your config with –global).
• dexaflow target list - List the targets, marking the one in use.
• dexaflow target remove - Remove a target (from the workspace file, or your config with –global).
• dexaflow target use - Select the target commands use when no –target is given.