AAC Docs

aac tenant api-key issue

AAC CLI 0.2.8MarkdownDocs 6b7d8268ba78

Issue and stage a second ACTIVE API key exactly once.

Synopsis

aac tenant api-key issue
  [-h]
  [--profile PROFILE]
  [--admin-url ADMIN_URL]
  [--data-plane-url DATA_PLANE_URL]
  [--output {json,table}]
  [--tenant-id TENANT_ID]
  [--new-key-file NEW_KEY_FILE]

Arguments

Argument Type Required Default Description
-h, --help flag no — show this help message and exit
--profile value no — Profile to run under (selection: --profile > AAC_PROFILE > reserved baseline main). aac profile list shows what exists.
--admin-url value no — Admin-surface base URL (overrides profile).
--data-plane-url value no — Data-plane-surface base URL (overrides profile).
--output json | table no json Output mode: json (the default) or table.
--tenant-id value no — Tenant to rotate (defaults to the selected profile identity).
--new-key-file value no — New staged credential path. Defaults to ~/.aac/credentials/<tenant-id>.next; existing files and symlinks are never overwritten.

Output

--output json (the default) prints one JSON document to standard output; --output table prints a readable table instead. Progress notes and diagnostics go to standard error, so the JSON stays parseable.

Exit codes

Code Meaning
0 Success.
1 The control plane or the identity provider rejected the request.
2 Usage error: an invalid flag, value or flag combination.
3 A local configuration or state problem: profile, credential file, cached session or agent.
4 Transport failure: an endpoint could not be reached.

Notes

The CLI saves a non-secret issuance identity before sending one request and writes plaintext only to a new mode-0600 staged file. It never replaces the current profile credential or retries automatically. After an ambiguous result, rerun this exact command.