fix(deploy): support a non-standard S3 port for the pgBackRest endpoint
CI / changes (pull_request) Successful in 2s
CI / unit (pull_request) Successful in 10s
CI / integration (pull_request) Successful in 19s
CI / ui (pull_request) Successful in 1m8s
CI / conformance (pull_request) Successful in 10s
CI / gate (pull_request) Successful in 1s
CI / deploy (pull_request) Successful in 1m43s
CI / changes (pull_request) Successful in 2s
CI / unit (pull_request) Successful in 10s
CI / integration (pull_request) Successful in 19s
CI / ui (pull_request) Successful in 1m8s
CI / conformance (pull_request) Successful in 10s
CI / gate (pull_request) Successful in 1s
CI / deploy (pull_request) Successful in 1m43s
The S3 endpoint is a host only; some providers publish a separate, non-443 port. Add an optional PGBACKREST_S3_PORT (default 443) alongside the endpoint host, wired through the prod overlay, write-prod-env.sh and both prod workflows, and clarify in the docs that the endpoint variable takes the host alone.
This commit is contained in:
@@ -79,6 +79,7 @@ export GATEWAY_ABUSE_BAN_ENABLED='true'
|
||||
# on (deploy/README.md). Empty repository values are harmless while the mode is off.
|
||||
export PGBACKREST_ARCHIVE_MODE='${PGBACKREST_ARCHIVE_MODE:-off}'
|
||||
export PGBACKREST_S3_ENDPOINT='$PGBACKREST_S3_ENDPOINT'
|
||||
export PGBACKREST_S3_PORT='${PGBACKREST_S3_PORT:-443}'
|
||||
export PGBACKREST_S3_BUCKET='$PGBACKREST_S3_BUCKET'
|
||||
export PGBACKREST_S3_REGION='$PGBACKREST_S3_REGION'
|
||||
export PGBACKREST_S3_KEY='$PGBACKREST_S3_KEY'
|
||||
|
||||
Reference in New Issue
Block a user