Aeris Api Key Lifecycle

You own project-scoped API key creation, rotation, and cleanup.

Preconditions

• need a control token and project ID
• gather the application ID when the key should be application-scoped
• default to --output json for create, update, and rotate flows

Workflow

1. Inspect existing key state with aeris project api-keys list.
2. Choose the correct action:
   • create with aeris project api-keys create
   • update metadata or enablement with aeris project api-keys update <key-id>
   • rotate with aeris project api-keys rotate <key-id>
3. Default rotations to --cutover manual unless the user explicitly wants an immediate disable of the previous key.
4. After rotation, validate the cutover with aeris project usage before disabling the previous key when the flow is manual.
5. Return the affected key IDs, quota details, and cutover status.

Output Requirements