opschain admin jsm-connections update
integrations:jira-service-management
Updates a JSM connection. A supplied --api-token-ref re-pins the
reference; an inline token (via --api-token-env or
--api-token-prompt) rotates the stored vault value and re-pins.
Enabling a disabled connection re-checks the
integrations:jira-service-management entitlement; disabling never
gates, so a lapsed estate can always unwind. A supplied
--project-keys replaces the stored scope (an empty value clears it).
opschain admin jsm-connections update limepoint-jsm --project-keys SUP,OPS
Updated JSM connection limepoint-jsm
Flags
| Flag | Meaning |
|---|---|
--server <url> | Server base URL (default: the active context / OPSCHAIN_SERVER). |
--auth-token <token> | Admin bearer token override (default: your opschain login session, then $OPSCHAIN_ADMIN_TOKEN, then the token stored by opschain admin login). |
--display-name <name> | Human-readable connection name. |
--base-url <url> | Replacement site base URL. |
--auth-email <email> | Replacement Atlassian account email (set to '' to switch to Data Center bearer authentication). |
--api-token-ref <ref> | Replacement secret-vault:// reference to re-pin. |
--api-token-env <name> | Environment variable holding the replacement API token / PAT. |
--api-token-prompt | Prompt for the replacement API token / PAT without echo. |
--project-keys <keys> | Replacement project-key scope (an empty value clears the scoping). |
--enabled | Whether the connection serves outbound writes (enabling re-checks the entitlement). |
See also
opschain docs cli/admin-jsm-connections-test— validate after a rotation.