fix: sync OpenAPI spec with backend (members field fix)#13
Open
fix: sync OpenAPI spec with backend (members field fix)#13
Conversation
…points) Updates the spec to match the current backend: - VirtualMembersListResponse: field renamed from "items" to "members" to match the Rust struct serialization - New upstream auth endpoints (PUT upstream-auth, POST test-upstream) - New fields on CreateRepositoryRequest (upstream_auth_type, etc.) - New RepositoryResponse fields (upstream_auth_type, upstream_auth_configured) The items/members mismatch caused the generated SDK to expect a different field name than what the backend actually returns, which could break the virtual members panel in the web UI. Ref artifact-keeper/artifact-keeper#461
|
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
1 participant
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.
Summary
Syncs the OpenAPI spec with the current backend state. Key fix:
VirtualMembersListResponse had its field named
itemsin the spec but thebackend serializes it as
members. This caused the generated SDK to expect adifferent field name than what the API actually returns, breaking the virtual
repo members panel in the web UI (reported in artifact-keeper/artifact-keeper#461).
Also includes new endpoints and types from the upstream auth feature (#451):
/repositories/{key}/upstream-auth/repositories/{key}/test-upstreamCreateRepositoryRequestandRepositoryResponseTest Checklist
SDK Impact