-
Notifications
You must be signed in to change notification settings - Fork 574
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
how to initiate a pgbackrest stanza-create? #3711
Comments
Hi @mzwettler2 Sorry you are running into issues. Would you be able to provide me with your manifest and steps? I did some simple testing where I changed buckets and I'm not seeing the same issue. |
Hi @ValClarkson Sorry for being unclear. When I change (reconfigure) the whole s3 bucket to a new one it works. If I only change (reconfgure) the repo1-path within the same s3 bucket to a new path it does not work ==>> Thanks |
i changed repo1-path too, and then i got the following error when running scheduled backup,
|
Sorry for the delay on this. I would think that if you are changing the path in the bucket you would want to set it up as a new repo. But the repo-path configuration isn't in the repo-host definition 🤔 @mzwettler2 How are you updating the repo path? Would you be able to provide a before and after spec where you are changing it? |
I define my S3 backup location using these CRDs: PostgresCluster.spec.backups.pgbackrest.repos[index].s3
PostgresCluster.spec.backups.pgbackrest
If I change the repo-path afterwards, the backup terminates incorrectly. I would have to do a stanza-create first - but that is not possible at the moment. pgo currently only does a stanza-create when you define a new repo or a new bucket. pgo should also do a stanza-create when the repo-path is changed. At the very least, however, there should be the option of triggering the execution of a new stanza-create with an annotation, for example. |
I would need an option to trigger the execution of a new stanza-create. Anything planned? |
Hi @mzwettler2. Thank you for the additional information. Just to verify what you are suggesting, you are effectively just looking for an imperative way to trigger a stanza-create using the configuration already set on the PostgresCluster spec? |
Yes.
Yes, that should work. The problem is that you would have to find out a lot of specific parameter values beforehand in order to be able to carry out the stanza-create suitable for PGO. this is not practicable for our customers. |
@mzwettler2 Understood. I can get something in our backlog for evaluation. In the meantime, I am curious if a command like
might be useful for this case. This assumes a cluster name of |
Thanks for adding something to your backlog. |
we are using s3 storage.
we have to change the whole s3 bucket and repo1-path for some reasons sometimes.
how can we get PGO to initiate a pgbackrest stanza-create if it does not find an existing repo?
it seems that PGO only triggers a pgbackrest stanza-create if there is a completely new configured pgbackrest.repo definition.
The text was updated successfully, but these errors were encountered: