Skip to content

openapi spec for advanced_pg + advanced_mysql#1167

Merged
DO-rrao merged 7 commits intodigitalocean:mainfrom
dweinshenker:advanced-pg-mysql
May 1, 2026
Merged

openapi spec for advanced_pg + advanced_mysql#1167
DO-rrao merged 7 commits intodigitalocean:mainfrom
dweinshenker:advanced-pg-mysql

Conversation

@dweinshenker
Copy link
Copy Markdown
Contributor

Add support for advanced_pg and advanced_mysql editions in the Managed Databases API spec

Copy link
Copy Markdown
Collaborator

@DO-rrao DO-rrao left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Automated Review Summary

Live API validation (GET /v2/databases/options) revealed spec-vs-production mismatches in the advanced_mysql version string and advanced_pg version_availability lifecycle dates. See inline comments for details.

Overall the structural changes (enum additions, model refs, options schema, layouts, sizes) are correctly wired and CI is green.

Comment thread specification/resources/databases/responses/options.yml
Comment thread specification/resources/databases/responses/options.yml
@@ -588,3 +789,21 @@ content:
end_of_availability: null
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Critical: advanced_pg version_availability has hardcoded EOL/EOA dates (e.g. eol: "2028-11-09T00:00:00Z" for v16), but the live API returns null for all three versions. Fabricating lifecycle dates that the API doesn't return will mislead consumers building version deprecation logic. These should be set to null to match production, or confirmed with the backend team if these dates are intentionally planned but not yet surfaced by the API.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The EOL dates are correct but not returned in the API properly (will be fixed). However, they reflect the open-source EOL dates for those version of PG and are accurate

Comment thread specification/resources/databases/databases_create_cluster.yml

PostgreSQL and MySQL Advanced Edition clusters can be provisioned by setting `engine` to
`advanced_pg` or `advanced_mysql`. Advanced Edition clusters are currently in public
preview. `advanced_pg` supports 1-, 2-, and 3-node deployments. `advanced_mysql` only
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Warning: The description mentions Advanced Edition is "in public preview" but doesn't explain what it offers over standard pg/mysql. A brief note on the key differences (e.g. features, performance characteristics) or a link to relevant documentation would help users decide which engine to provision.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Addressed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants