docs: Add feature gate instructions for PostgreSQL UI#25
Conversation
Add documentation explaining how to enable the PostgreSQL UI feature gates after installing the PostgreSQL operator. Includes: - Feature gate names (middleware-rds-postgresql, middleware-rds-postgresql-backup) - Access URL pattern for the feature gate page - Note about Alpha features requiring the Alpha Feature toggle - Verification steps Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
WalkthroughAdded documentation for enabling PostgreSQL UI feature gates in the web console, including prerequisites, step-by-step procedures for activating specific feature gates (middleware-rds-postgresql and middleware-rds-postgresql-backup), and verification instructions. No functional or code logic changes. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
📝 Coding Plan
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment Tip CodeRabbit can approve the review once all CodeRabbit's comments are resolved.Enable the |
Deploying alauda-postgresql with
|
| Latest commit: |
fe37030
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://aba92a78.alauda-postgresql.pages.dev |
| Branch Preview URL: | https://docs-add-feature-gate-instru.alauda-postgresql.pages.dev |
There was a problem hiding this comment.
🧹 Nitpick comments (2)
docs/en/installation.mdx (2)
109-119: Make required vs optional gates explicit and remove procedural duplication.Lines 109-119 currently describe enabling gates twice. Consider collapsing this into one action list and explicitly marking
middleware-rds-postgresqlas required and backup as optional.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/en/installation.mdx` around lines 109 - 119, Collapse the duplicated gate-enabling steps into a single concise action: present a single table or list that clearly marks middleware-rds-postgresql as "Required" and middleware-rds-postgresql-backup as "Optional (backup/restore UI)", and remove the second procedural bullet that repeats enabling them; update the section around the current table and the subsequent bullet list that references `middleware-rds-postgresql` and `middleware-rds-postgresql-backup` so they are expressed once with explicit required/optional labels (use the gate names middleware-rds-postgresql and middleware-rds-postgresql-backup to locate the text to edit).
105-108: Clarify the URL placeholder to avoid path ambiguity.Line 107 changes from a
/console-portal/example URL to a/console-platform/feature-gatedestination, which may be read as string concatenation and confuse users. Use a host-only placeholder instead.Suggested doc edit
-1. Navigate to the Feature Gate page: - - Access the feature gate configuration at `{platform-access-address}/console-platform/feature-gate` - - For example, if your platform access address is `https://demo.example.com/console-portal/`, the feature gate page would be `https://demo.example.com/console-platform/feature-gate` +1. Navigate to the Feature Gate page: + - Access the feature gate configuration at `https://{platform-host}/console-platform/feature-gate` + - For example, if your platform host is `demo.example.com`, the feature gate page is `https://demo.example.com/console-platform/feature-gate`🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/en/installation.mdx` around lines 105 - 108, The example URL is ambiguous because it mixes a full example path (/console-portal/) with the destination path (/console-platform/feature-gate); update the text to use a host-only placeholder for {platform-access-address} (e.g., https://demo.example.com) and show the final feature gate URL by appending /console-platform/feature-gate to that host, replacing the current /console-portal/ example; ensure references include the exact placeholders/paths `{platform-access-address}`, `/console-portal/`, and `/console-platform/feature-gate` so readers clearly understand how to construct the URL.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In `@docs/en/installation.mdx`:
- Around line 109-119: Collapse the duplicated gate-enabling steps into a single
concise action: present a single table or list that clearly marks
middleware-rds-postgresql as "Required" and middleware-rds-postgresql-backup as
"Optional (backup/restore UI)", and remove the second procedural bullet that
repeats enabling them; update the section around the current table and the
subsequent bullet list that references `middleware-rds-postgresql` and
`middleware-rds-postgresql-backup` so they are expressed once with explicit
required/optional labels (use the gate names middleware-rds-postgresql and
middleware-rds-postgresql-backup to locate the text to edit).
- Around line 105-108: The example URL is ambiguous because it mixes a full
example path (/console-portal/) with the destination path
(/console-platform/feature-gate); update the text to use a host-only placeholder
for {platform-access-address} (e.g., https://demo.example.com) and show the
final feature gate URL by appending /console-platform/feature-gate to that host,
replacing the current /console-portal/ example; ensure references include the
exact placeholders/paths `{platform-access-address}`, `/console-portal/`, and
`/console-platform/feature-gate` so readers clearly understand how to construct
the URL.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: ac90b55f-177d-4d82-a7c1-090a068c30f8
📒 Files selected for processing (1)
docs/en/installation.mdx
Add documentation explaining how to enable the PostgreSQL UI feature gates after installing the PostgreSQL operator. Includes:
Summary by CodeRabbit