feat: expose S3 custom endpoint for fallback CP#288
Conversation
Add the endpoint field to the aws_s3 configuration comments in values.yaml, allowing users to specify an S3-compatible endpoint (MinIO, Ceph, Aliyun OSS, etc.) for the Fallback CP feature. The gateway code already supports this field via the lua-resty-aws-s3 library (AWS SDK v2 BaseEndpoint), it was just not documented in the helm chart. Bump chart version: 0.2.66 -> 0.2.67
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
✅ Files skipped from review due to trivial changes (3)
📝 WalkthroughWalkthroughBump Helm chart versions for gateway and api7, and add commented optional S3-compatible endpoint settings in both charts' values files and the api7 README badge. ChangesGateway Helm Chart Update
api7 Helm Chart Update
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested reviewers
🚥 Pre-merge checks | ✅ 6✅ Passed checks (6 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Pull request overview
Adds the endpoint field to the documented aws_s3 config in the gateway chart's values.yaml, enabling users to discover S3-compatible endpoint support (MinIO, Ceph, Aliyun OSS) for the Fallback CP feature, and bumps the chart version accordingly.
Changes:
- Document an optional
endpointfield underdeployment.fallback_cp.aws_s3invalues.yamlcomments. - Bump chart version from 0.2.66 to 0.2.67.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| charts/gateway/values.yaml | Adds commented endpoint field to aws_s3 fallback CP configuration |
| charts/gateway/Chart.yaml | Bumps chart version 0.2.66 → 0.2.67 |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Add the custom_endpoint field to the aws_s3 configuration comments in the api7 chart values.yaml. The dashboard code already supports this field (mapstructure:"custom_endpoint" in s3_store.go). Note: the gateway chart uses 'endpoint' while the dashboard uses 'custom_endpoint' — these are separate config paths read by different components. Bump api7 chart version: 0.18.0 -> 0.18.1
The Fallback CP feature already supports connecting to S3-compatible storage (MinIO, Ceph, Aliyun OSS, etc.) in both the gateway and dashboard code. However, the
endpoint/custom_endpointfields were missing from the helm charts'values.yaml, making them undiscoverable for users.This PR exposes the endpoint configuration in both charts:
Gateway chart (
charts/gateway):endpointfield todeployment.fallback_cp.aws_s3commentsAPI7 chart (
charts/api7):custom_endpointfield tofallback_cp.aws_s3commentsNote: the field name differs between components — gateway uses
endpoint(matchinglua-resty-aws-s3FFI signature) while dashboard usescustom_endpoint(Gomapstructuretag ins3_store.go). Both map to AWS SDK v2'sBaseEndpoint.Summary by CodeRabbit
New Features
Chores
Documentation