SwitchServiceAccountsToImpersonation
Switches the pipeline service accounts of the tenant from stored client secrets to impersonation. Dry run by default; --apply runs the switch.
Examples
Dry run: show what the switch would do, change nothing:
octo-cli -c SwitchServiceAccountsToImpersonation
Apply the switch without the confirmation prompt (CI/automation):
octo-cli -c SwitchServiceAccountsToImpersonation -a -y
Dry run, report as JSON:
octo-cli -c SwitchServiceAccountsToImpersonation -j
Options
| Short | Long | Required | Description |
|---|---|---|---|
-a | --apply | no | Run the switch (default is a dry run that changes nothing) |
-rdf | --redeployDataFlows | no | true or false: redeploy the affected data flows after the switch (default true) |
-y | --yes | no | Skip confirmation prompt |
-j | --json | no | Output the report as raw JSON |
Notes
Always run the dry run first and read the outcome per account. Without --apply nothing is written and no confirmation is asked.
Apply is destructive: stored client secrets are cleared and the old secrets are invalidated identity-side. The server refuses it (exit -5) unless the installation sets OCTO_SERVICEACCOUNTIMPERSONATION__ALLOWSECRETCLEARING=true.
Two-phase flow: accounts reported as SwitchedPendingInvalidation are switched, but the old secret is only invalidated once the data flows are redeployed. Re-run with --redeployDataFlows true to complete the switch.
--redeployDataFlows (default true) redeploys the affected data flows after the switch. Data flows that fail to redeploy are listed and make the command exit with -5.
A Failed account makes the command exit with -5 after the full report was printed.
The tenant is the tenant of the active context. Neither client secrets nor tokens are ever printed: the report contains none.