fix(api): allow missing custom hostname validation records#5543
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: 32126a44a2
ℹ️ About Codex in GitHub
Your team has set up Codex to 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 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 32126a44a2
ℹ️ About Codex in GitHub
Your team has set up Codex to 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 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Supabase CLI previewnpx --yes https://pkg.pr.new/supabase@5543Preview package for commit |
…5543) Updates the temporary Management API OpenAPI overrides so custom-hostname SSL validation records are optional while the backend response is inconsistent with the published schema. The generated API contract now accepts responses where `data.result.ssl.validation_records` is absent. The legacy domains formatter treats the absent field like the Go CLI nil-slice behavior when rendering human-readable status output. This prevents domain commands from failing at schema decode time when staging returns a custom-hostname response without outstanding SSL validation records.
2 participants
Updates the temporary Management API OpenAPI overrides so custom-hostname SSL validation records are optional while the backend response is inconsistent with the published schema.
The generated API contract now accepts responses where
data.result.ssl.validation_recordsis absent. The legacy domains formatter treats the absent field like the Go CLI nil-slice behavior when rendering human-readable status output.This prevents domain commands from failing at schema decode time when staging returns a custom-hostname response without outstanding SSL validation records.