--profile <name> on supported commands when you have a stored Service Account profile. Run a command family without a subcommand to display its built-in help.
For one copy-ready command example per command, continue to CLI examples.
Identity availability
A human PAT can use every API-backed command below when RBAC permits it. Local commands such aslogin and generate do not require API authorization. A Service Account can use only:
Core record commands
generate only returns locally generated fields. new generates, encrypts and stores them. set updates a matching record or creates it when human mode has enough information.
Project commands
Record management commands
--scope-type project and --scope-id.
Gateway commands
Discovery and lifecycle:Service Account metadata commands
Argument rules
- Values in angle brackets are required. Values in square brackets are optional.
- UUID arguments must be complete IDs. Names are not accepted where an ID is required.
--accountselects account context. It does not add permissions.--projectlimits an operation to one project.--profileselects a stored Service Account profile for commands that support machine identity.- Repeat
--field key=valueand--credential <id>when you need more than one value. - Use
nullonly where the command syntax explicitly accepts it. It clears the stored optional value. - Use
noneonly where documented. It replaces a list with an empty list. - Boolean flags accept only
trueorfalse.
Output
Normal commands write formatted JSON to stdout. Scripts should read stdout as JSON and use the process exit status to decide whether the operation completed. Diagnostic text and stable error codes go to stderr. Commands that return no resource print{ "ok": true }.
Complete workflow examples
Create and inspect a project:CLI failures
The CLI never treats an incomplete Service Account profile as a human login. Fix the profile instead of
adding a human PAT to the same machine configuration.