Skip to content

fix: correct version-lookup endpoint in ManagedDatabase troubleshooting - #93

Open
lmilbaum wants to merge 1 commit into
polarsquad:mainfrom
lmilbaum:fix/pr-65-audit-fixes
Open

lmilbaum wants to merge 1 commit into
polarsquad:mainfrom
lmilbaum:fix/pr-65-audit-fixes

Conversation

@lmilbaum

@lmilbaum lmilbaum commented Oct 3, 2026

Copy link
Copy Markdown
Contributor

Summary

Fixes the troubleshooting guidance in docs/development.md introduced by PR #65.
The paragraph told maintainers to run GET /1.3/database/plans to find valid
properties.version values when a e2e Ready wait fails with a 400. That endpoint
returns compute plan shapes (e.g. 1x1xCPU-2GB-25GB), not engine versions.

Change: points the guidance at GET /1.3/database/service-types/{type} (e.g.
GET /1.3/database/service-types/pg), names the response fields to read
(properties.version.enum for the accepted set, latest_available_version for the
newest), and adds a clarifying sentence that /database/plans lists plan shapes.

Addresses issues identified in the #65 audit.

Reviewer summary

HIGH finding fully resolved. No new HIGH or MEDIUM issues introduced. One LOW noted
(field name accuracy) — field names verified against vendored SDK upcloud-go-api v8.41.0 (upcloud.ManagedDatabaseType.LatestAvailableVersion and
ManagedDatabaseServiceProperty.Enum).

🤖 Generated with Claude Code

- docs/development.md: replace incorrect `GET /1.3/database/plans` with
  `GET /1.3/database/service-types/{type}` for engine-version discovery
- Add `properties.version.enum` and `latest_available_version` field names
- Clarify that `/database/plans` returns compute shapes, not engine versions

Addresses audit finding from PR polarsquad#65 review.

Co-Authored-By: Claude Haiku 4.5 <[email protected]>
@lmilbaum
lmilbaum marked this pull request as ready for review October 3, 2026 06:06

This branch has not been deployed

No deployments
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.

1 participant