Skip to content

build: use shared S3 addressing style support - #1

Draft
davidchandra95 wants to merge 1 commit into
mainfrom
feat/cos-addressing-style-staging
Draft

build: use shared S3 addressing style support#1
davidchandra95 wants to merge 1 commit into
mainfrom
feat/cos-addressing-style-staging

Conversation

@davidchandra95

Copy link
Copy Markdown
Owner

Summary

Build the plugin manager and PostgreSQL instance-sidecar from the shared Barman fix, and add the generated CRD field spec.configuration.s3AddressingStyle.

Why

Tencent COS rejects path-style S3 URLs. The existing plugin could set virtual-host style for base backup and WAL paths only, leaving catalog, retention, and recovery commands on path-style URLs.

Temporary staging bridge

This fork replaces the Barman Cloud dependency with the pinned fix from cloudnative-pg/barman-cloud#290. Remove the replace directive once an upstream plugin release includes that library revision.

Validation

  • GOWORK=off go test $(GOWORK=off go list ./... | rg -v /test/e2e$)
  • amd64 manager image build, which downloaded the pinned forked library

The draft PR workflow publishes matching manager and sidecar images for the staging deployment draft.

@davidchandra95
davidchandra95 force-pushed the feat/cos-addressing-style-staging branch 2 times, most recently from 610c17a to 6cb5c26 Compare August 10, 2026 08:19
Signed-off-by: david <slowtyper@davids-MacBook-Pro-2.local>
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