Repository navigation
update rc openapi spec - #4504
Open
github-actions[bot] wants to merge 3 commits into
Open
github-actions[bot] wants to merge 3 commits into
github-actions[bot] wants to merge 3 commits into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
update rc openapi spec
Note
Low Risk
Documentation-only OpenAPI updates with no runtime code changes; operationId changes could affect regenerated API clients if they key off those names.
Overview
Regenerates or syncs
content/operate/rc/api/api-reference/openapi.jsonso published API docs match the current backend contract.Data Integration workspace proxy paths (
/v1/subscriptions/{subscriptionId}/data-integration-workspaceand.../**) get updatedoperationIdvalues across GET/PUT/POST/DELETE/PATCH (e.g. suffix renumbering likeproxyDataIntegrationWorkspace_2→_3). Paths and summaries are unchanged; only client-generator identifiers shift.Agent Memory store operations (
listMemoryStores, get store, create API key, delete API key, etc.) reorder documented response entries in the spec—mostly moving 403 and 404 (and in one case 201/401) relative to other status codes. Wording of each status description is effectively the same; the diff is spec structure/ordering, not new or removed error types.Reviewed by Cursor Bugbot for commit fd0a30b. Bugbot is set up for automated code reviews on this repo. Configure here.