Skip to content

Multiple applications and Profiles ​

Examples use goodvision. After a project installation, use npx --no-install goodvision. See quick start for installation and first configuration.

Add an application to an existing configuration without changing the default. For the first profile, config init --name <name> selects its name:

bash
goodvision profile add --config ./goodvision.json --name second-sandbox \
  --api-base "$GOODVISION_API_BASE" \
  --docs-origin "$GOODVISION_DEVELOPER_DOCS_ORIGIN" \
  --application "$GOODVISION_SECOND_APPLICATION_ID" \
  --environment sandbox --token-file ./second-token
goodvision profile list --config ./goodvision.json
goodvision context --config ./goodvision.json --profile second-sandbox
goodvision profile use second-sandbox --config ./goodvision.json

profile list reports applications, environments, credential kinds and the default marker without reading or exposing credentials. profile add rejects duplicate names. Only profile use persists a new default. Concurrent scripts should select --profile per invocation. Concurrent edits fail without changing the original configuration; investigate a leftover .lock only after confirming no editor is active.

Rename or remove a Profile ​

bash
goodvision profile rename second-sandbox reader --config ./goodvision.json
goodvision profile use sandbox --config ./goodvision.json
goodvision profile remove reader --yes --config ./goodvision.json

rename preserves the application, environment and credential references; renaming the active entry updates its name. remove requires --yes and rejects the active Profile. Select another Profile first; the last entry cannot be removed. Credential files remain available to other applications, and server authorization is unchanged.

CommandPurpose
profile listList application contexts
profile add --name <name> ...Add without overwriting or switching
profile use <name>Persist the default selection
profile rename <old> <new>Rename without changing identity
profile remove <name> --yesRemove an inactive configuration
--profile <name> <command>Select context for one invocation

Developer documentation. Internal operations access is not required.