Skip to content

feat(compute): sync 1.9.x console spec with current compute database API#73

Open
abnegate wants to merge 3 commits into
mainfrom
feat-compute-api
Open

feat(compute): sync 1.9.x console spec with current compute database API#73
abnegate wants to merge 3 commits into
mainfrom
feat-compute-api

Conversation

@abnegate

@abnegate abnegate commented Jun 8, 2026

Copy link
Copy Markdown
Member

Updates the compute database paths and dedicatedDatabase* models in the 1.9.x console spec to match the current cloud branch: credential rotation moved POST -> PATCH, added listDatabaseSpecifications and backup policy endpoints, removed logs/usage endpoints. Only the compute service is touched; all other services are byte-identical to the parent commit.

What does this PR do?

(Provide a description of what this PR does.)

Test Plan

(Write your test plan here. If you changed any code, please provide us with clear instructions on how you verified your changes work.)

Related PRs and Issues

(If this PR is related to any other PR or resolves any issue or related to any issue link all related PR and issues here.)

Have you read the Contributing Guidelines on issues?

(Write your answer here.)

Updates the compute database paths and dedicatedDatabase* models in the
1.9.x console spec to match the current cloud branch: credential rotation
moved POST -> PATCH, added listDatabaseSpecifications and backup policy
endpoints, removed logs/usage endpoints. Only the compute service is
touched; all other services are byte-identical to the parent commit.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings June 8, 2026 03:22

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

@greptile-apps

greptile-apps Bot commented Jun 8, 2026

Copy link
Copy Markdown

Greptile Summary

This PR makes three small correctness fixes in the 1.9.x console OpenAPI spec, all within the compute service. No other services are touched.

  • Strips the erroneous four-space indent from the computeListDatabaseBackupPolicies and computeCreateDatabaseBackupPolicy endpoint descriptions, aligning them with the rest of the spec.
  • Replaces the invalid type: object + items pattern on the pricing property (only meaningful for arrays) with the correct OpenAPI 3 form: allOf containing a $ref to dedicatedDatabaseSpecificationPricing, so validators will now actually enforce the schema.

Confidence Score: 5/5

Safe to merge — all three changes are narrow spec corrections with no risk of regressions.

The changes are minimal and mechanical: two description string trims and one schema structure fix (itemsallOf). The allOf form is the correct OpenAPI 3 pattern for constraining an object shape via $ref, so the fix is unambiguously right. No logic, no new endpoints, no behaviour changes.

No files require special attention.

Important Files Changed

Filename Overview
specs/1.9.x/open-api3-1.9.x-console.json Three targeted fixes: leading whitespace stripped from two backup-policy endpoint descriptions, and the pricing property corrected from type: object + items to a proper allOf + $ref for OpenAPI 3 compliance.

Reviews (2): Last reviewed commit: "fix(specs): address review feedback on c..." | Re-trigger Greptile

Comment thread specs/1.9.x/open-api3-1.9.x-console.json Outdated
Comment thread specs/1.9.x/open-api3-1.9.x-console.json Outdated
Comment thread specs/1.9.x/open-api3-1.9.x-console.json Outdated
abnegate and others added 2 commits June 10, 2026 17:20
Resolves conflicts in specs/1.9.x/open-api3-1.9.x-console.json in favour
of main, which already absorbed this branch's compute sync via the
auto-generated spec update (#74) and additionally reflects the removal
of the redundant getDatabaseInsights/getDatabaseMetrics endpoints from
the cloud API.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Use allOf instead of the array-only items keyword for the pricing
property on dedicatedDatabaseSpecificationList so the referenced
object shape is actually enforced, and strip the leading indentation
from the backup-policy endpoint descriptions for consistency with the
rest of the spec.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.

2 participants