# Pipelines Advanced Reference ## Setup ```sh agentia auth set --adv agentia adv auth status --json ``` Authentication is global by default. Add `--local` to `auth set` for current-project/current-user scope; the PAT still stays in the keychain. Remove global auth with `auth unset --adv [--global]` or local auth with `auth unset --adv --local`; JSON/non-interactive removal requires `--yes`. Use `--adv-base-url` only for approved non-standard endpoints. ## Deployment Journey ```sh agentia adv organization list --json agentia adv organization validate agentia adv deployment create --name release-1 --source-org --target-org agentia adv deployment options --set deployOptionsIgnoreWarnings=false agentia adv component types --json agentia adv component list --flow --type ApexClass --json agentia adv component add --component ApexClass/Foo agentia adv deployment validate --wait --json agentia adv deployment deploy --yes --wait --json agentia adv job get --json ``` ## Notes - `deployment list` exposes the API `flowId` as `id`; do not use the raw list row link id. - `deployment list` returns at most 500 rows and has no filter. - `deployment options` reads current options, merges `--set` or `--file`, and sends the complete options object because the API replaces the entire object. `--set` converts exact booleans/null and finite JavaScript Number forms, including hex and exponent notation. Unknown option names can be silently dropped; verify saved options with `deployment get --json`. Rejected values can return HTTP 400 with no provider detail. The server owns the complete option catalog. - `component types` can report the same type name in several views. - `component add` and `component remove` accept `--component Type/Name`. Add supports a text `--file`; remove does not. `--json-file` must be a bare array and accepts `{type, fullName}`, rows extracted from `result.components`, or `{nodeType: {name}, fullName}`. Remove returns the submitted array in `requested`, not a count. - `validate`, `deploy`, `quick-deploy`, and `cancel` are asynchronous; use `--wait` or `agentia adv job wait`. A timeout stops only the CLI wait; the run continues and the JSON error includes the last observed job. - `deploy`, `quick-deploy`, and `cancel` prompt interactively. JSON and non-interactive runs require `--yes`; matching MCP tools require `confirm: true`. - `quick-deploy --backup` invokes the server's `backupThenDeploy` action instead of a quick deploy. The CLI refuses a quick deploy only when the latest job explicitly reports `canQuickDeploy: false`; validate with tests first. - Polling defaults to 3 seconds with a 3600-second timeout. Failed or cancelled waited runs exit nonzero; JSON errors include the normalized job. - `job list` excludes validation runs. Page numbering starts at 0, page size defaults to 50, and the server caps it at 100. - API JSON errors expose sanitized code/status/method/URL/name/message plus `transactionId`; validation errors expose only safe fields plus `transactionId`, never parser state or command configuration. ## MCP Argument Names - Organizations use `id`. All deployment-scoped tools use canonical `deploymentId`; legacy `id` and `flow` aliases remain accepted but cannot disagree. - Deployment validate: `deploymentId`, optional `wait`, `interval`, `timeout` (no confirmation). - Deploy: the validation inputs plus `confirm: true`. - Quick deploy: deploy inputs plus optional `backup`. - Cancel: `deploymentId`, `confirm: true`, optional `wait`, `interval`, `timeout`. - Component add/remove: `deploymentId`, `components` (`Type/Name` strings or `{type, fullName, excluded?}` objects). - Job list: `deploymentId`, optional `page`, `pageSize`.