[Backport release-1.1] [bucket] Fix s3manager endpoint mismatch with COSI credentials by github-actions[bot] · Pull Request #2215 · cozystack/cozystack
…Info The deployment template was constructing the S3 endpoint from the tenant's namespace host (e.g. s3.freedom.infra.example.com), while COSI credentials are issued for the actual SeaweedFS endpoint (e.g. s3.infra.example.com). This mismatch caused 'invalid credentials' errors when users tried to log in with valid credentials from the bucket secret. Now the endpoint is resolved from BucketInfo (same source as credentials), with a fallback to the constructed namespace host for first-time deploys before BucketAccess secrets are created. Signed-off-by: IvanHunters <xorokhotnikov@gmail.com> (cherry picked from commit f647cfd)
kvaps
deleted the
backport-2211-to-release-1.1
branch
This PR changes 10-29 lines, ignoring generated files.
Something isn't working
labels
Mar 13, 2026This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters