Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: add custom env to logical backup #1973

Closed

Conversation

farodin91
Copy link
Contributor

@farodin91 farodin91 commented Jul 25, 2022

fixes #1473

codegen failed with

./hack/update-codegen.sh                                  
Generating deepcopy funcs
Generating clientset for acid.zalan.do:v1 zalando.org:v1 at github.com/zalando/postgres-operator/pkg/generated/clientset
Generating listers for acid.zalan.do:v1 zalando.org:v1 at github.com/zalando/postgres-operator/pkg/generated/listers
Generating informers for acid.zalan.do:v1 zalando.org:v1 at github.com/zalando/postgres-operator/pkg/generated/informers
cp: cannot stat 'github.com/zalando/postgres-operator/pkg/*': No such file or directory

@farodin91 farodin91 force-pushed the add-custom-env-to-logical-backup branch from 0613e36 to 04cf023 Compare July 25, 2022 14:33
@FxKu FxKu added this to the 2.0 milestone Dec 14, 2022
@FxKu
Copy link
Member

FxKu commented Jan 23, 2024

Since we merged #2051 this PR seems to be obsolete. I hope you don't mind if I close it. We might think of passing env variables from the cluster manifest to the logical backup pod, too. But I don't really like to have an EnvVar section for logical backup in the Postgresql manifest itself.

@FxKu FxKu closed this Jan 23, 2024
@FxKu FxKu removed this from the 1.11.0 milestone Jan 23, 2024
@farodin91 farodin91 deleted the add-custom-env-to-logical-backup branch January 23, 2024 14:36
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.

How can I pass AWS_SESSION_TOKEN to logical backup cron job
2 participants