Skip to content

fix(databases): describe regions as plain region codes - #236

Merged
subnetmarco merged 2 commits into
mainfrom
docs/region-placeholder
Sep 27, 2026
Merged

subnetmarco merged 2 commits into
mainfrom
docs/region-placeholder

Conversation

@subnetmarco

@subnetmarco subnetmarco commented Sep 26, 2026 •

Copy link
Copy Markdown
Member

Summary

The CLI told users to type region IDs that name the provider behind Volcano.

  • databases create --region help said aws-<aws-region>, e.g. aws-us-east-1. It now reads "Database region, such as us-east-1".
  • docs/databases.md: the command table shows --region <region>, and the example uses --region us-east-1.
  • durable schedulers create help example passed --regions aws-us-east-1. Scheduler regions are function region codes, which have always been plain, so it now passes us-east-1.

Merge order

Merge after Kong/volcano-hosting#1478 is deployed. That change makes the API publish us-east-1 for database regions and accept both forms. Before it, the API only accepts aws-us-east-1 for databases, so a user following the new help would get a 400.

The unit-test fixtures and tests/e2e/api default still use aws-us-east-1. Those are mock payloads and a staging default, and the API keeps accepting that form.

Validation

  • go build ./... passes.
  • go test ./internal/cmd/databases/... ./internal/cmd/durable/... passes.
  • The shared docs lint passes on docs/.

The create row described --region as aws-<aws-region>. Call it a region, as the rest of the platform docs do.

Co-authored-by: Cursor <cursoragent@cursor.com>
Copilot AI balanced review requested due to automatic review settings September 26, 2026 23:51
@subnetmarco
subnetmarco requested a review from a team as a code owner September 26, 2026 23:51

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.

The databases create flag help described regions as aws-<aws-region>, and the durable scheduler example passed --regions aws-us-east-1, although scheduler regions have always been plain codes. The API now publishes database region IDs as us-east-1 and still accepts the older form.

Co-authored-by: Cursor <cursoragent@cursor.com>
@subnetmarco subnetmarco changed the title docs(databases): drop the AWS region placeholder fix(databases): describe regions as plain region codes Sep 27, 2026
@subnetmarco
subnetmarco merged commit d8211fb into main Sep 27, 2026
11 of 12 checks passed
@subnetmarco
subnetmarco deleted the docs/region-placeholder branch September 27, 2026 21:59
@kong-volcano-app kong-volcano-app Bot mentioned this pull request Sep 27, 2026
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