Split branch resource into Vitess & Postgres branches #178
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
joemiller
approved these changes
Dec 9, 2025
Base automatically changed from
joshmgross/unsupported-resources-roles
to
speakeasy
December 9, 2025 20:21
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Similar to #166, this creates a branch resource per database kind - currently Vitess and Postgres.
This allows us to simplify resource management within the provider and avoid inconsistencies due to differing API responses and support.
The resources right now were manually copied, but once
speakeasysupports thecopyoverlay (speakeasy-api/openapi#87) we'll be able to use that and reduce the amount of manual documentation.