Skip to content

Add v1/config/CommandCenterGroup and the command-center-groups commands - #142

Draft
bg451 wants to merge 4 commits into
mainfrom
bg451/chronoctl-sync-swagger-command-center-groups
Draft

bg451 wants to merge 4 commits into
mainfrom
bg451/chronoctl-sync-swagger-command-center-groups

Conversation

@bg451

@bg451 bg451 commented Sep 23, 2026 •

Copy link
Copy Markdown
Collaborator

Syncs the public API swagger specs.

CommandCenterGroup is now available on the stable v1 config API at /v1/config/command-center-groups. This adds the generated configv1 client and models for it and a new chronoctl command-center-groups command group with the usual create, read, update, delete, list and scaffold subcommands. The unstable client keeps its command center group operations until the unstable endpoints are removed.

Held as a draft until the v1 command center group endpoints are available on the API. Mark it ready once they are, after re-running the sync if the spec has changed in the meantime.

Re-syncs the public API specs. CommandCenterGroup is now available on
the stable v1 config API, so the v1 client, models and CLI gain
command-center-groups support. The unstable client keeps its command
center group operations until the unstable endpoints are removed.

Also picks up the removal of the GCP_US_LOS_ANGELES synthetic test
location.
@bg451

bg451 commented Sep 23, 2026

Copy link
Copy Markdown
Collaborator Author

agentd

Asset Viewer Owner
🖥 Agent   open     open  
📄 Document   open     open  

…t location

Regenerated against the current public API spec, which serves the
GCP_US_LOS_ANGELES location again. The command center group client, models
and commands are unchanged.
The location is back in the current spec, so the sync no longer removes it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant