chore(api): sync Management API OpenAPI spec - #6377
chore(api): sync Management API OpenAPI spec#6377supabase-cli-releaser[bot] wants to merge 1 commit into
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: f2c5eefbb4
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| backend_type: Schema.Literals([ | ||
| "postgres", | ||
| "bigquery", | ||
| "clickhouse", |
There was a problem hiding this comment.
When a caller creates a postgres or bigquery drain, this input still advertises those backend_type literals, but the adjacent config union has dropped the hostname/schema/port and project_id/dataset_id branches that were present before. makeSupabaseApiClient.execute decodes through this generated input schema before serializing, so a previously supported valid payload is no longer representable by OperationInput and its backend-specific config cannot survive validation. Keep these request-side branches even if the response _Output schemas intentionally redact them.
Useful? React with 👍 / 👎.
Supabase CLI previewnpx --yes https://pkg.pr.new/supabase/cli/supabase@6aa6b14512ab5c4b0dd8d38c096c09681dc474ddPreview package for commit |
f2c5eef to
6aa6b14
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 6aa6b14512
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| name: Schema.optionalKey(Schema.String), | ||
| description: Schema.optionalKey(Schema.String), | ||
| config: Schema.optionalKey( | ||
| Schema.Union([ |
There was a problem hiding this comment.
The same request-side regression also affects the PUT operation: when updating a postgres or bigquery drain, backend_type still accepts those values, but this config union no longer includes their hostname/schema/port or project_id/dataset_id fields. Consequently, those valid update payloads are rejected by OperationInput or stripped during makeSupabaseApiClient.execute validation before the request is serialized; retain the backend-specific request schemas here even if response schemas redact them.
Useful? React with 👍 / 👎.
1 participant
This PR was automatically created to sync the generated
@supabase/apipackage with the latest Management API OpenAPI document.Changes were detected in the upstream OpenAPI documents exposed by
https://api.supabase.com/api/v1-jsonandhttps://api.supabase.com/api/v2-json.