Skip to content
Push

Fix PITR standby promotion issue by clearing recovery settings #7

Sign in to view logs

Fix PITR standby promotion issue by clearing recovery settings

Fix PITR standby promotion issue by clearing recovery settings #7

Triggered via push November 18, 2025 01:00
@jcrapuchettesjcrapuchettes
pushed c87acd2
master
Status Success
Total duration 3m 18s
Artifacts 3

push.yml

on: push
Build
15s
Build
Unit Tests
13s
Unit Tests
Staticcheck
27s
Staticcheck
Errcheck
16s
Errcheck
Matrix: Build Docker Images
Fit to window
Zoom out
Zoom in

Annotations

9 warnings
Unit Tests
Both go-version and go-version-file inputs are specified, only go-version will be used
Build
Both go-version and go-version-file inputs are specified, only go-version will be used
Errcheck
Both go-version and go-version-file inputs are specified, only go-version will be used
Staticcheck
Both go-version and go-version-file inputs are specified, only go-version will be used
Sensitive data should not be used in the ARG or ENV commands: pg15/Dockerfile#L25
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "AWS_SHARED_CREDENTIALS_FILE") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
Legacy key/value format with whitespace separator should not be used: pg16/Dockerfile#L55
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Sensitive data should not be used in the ARG or ENV commands: pg16/Dockerfile#L33
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "AWS_SHARED_CREDENTIALS_FILE") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
Legacy key/value format with whitespace separator should not be used: pg17/Dockerfile#L55
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Sensitive data should not be used in the ARG or ENV commands: pg17/Dockerfile#L33
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "AWS_SHARED_CREDENTIALS_FILE") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/

Artifacts

Produced during runtime
Name Size Digest
RedBalloon-work~postgres-flex~SDARDK.dockerbuild Expired
121 KB
sha256:29638477895fd49223edd15a6cd7a241dcf6d12eeca906de00ee4f479fdb6e1a
RedBalloon-work~postgres-flex~SQYRPJ.dockerbuild Expired
136 KB
sha256:b058739c134cf03183719ed4378d65a753dc6a534d109e8f04c597534584bc95
RedBalloon-work~postgres-flex~WFJIPF.dockerbuild Expired
123 KB
sha256:960c605ea1e4403d236d9f781933dc79ed3b50f5a4051aa8fb3d8c780ca63211