stanza name not correctly initialized when using a name different from the cluster name (default)

[fguiet]

Hi,

First, thank you for this great plugin

Here is my Archive Manifest

apiVersion: pgbackrest.cnpg.opera.com/v1
kind: Archive
metadata:
  name: s3-xxxx-k8s-dbaas-test
  namespace: pg-guiet-ns
spec:
  configuration:
    repositories:
      - destinationPath: /k8s-dbaas-test
        bucket: pg-backup-01-prod
        endpointURL: xxxx
        disableVerifyTLS: true                
        retention:
          archiveType: full
          full: 3
          fullType: count
        s3Credentials:       
          uriStyle: path
          region: "eu-west-3"
          accessKeyId:
            name: pgbackrest-s3-secret
            key: access-key-id
          secretAccessKey:
            name: pgbackrest-s3-secret
            key: secret-access-key
    stanza: pgbackrest
    compression: zst
    data:
      immediateCheckpoint: true
      jobs: 2
  instanceSidecarConfiguration:
    resources:
      requests:
        memory: "2Gi"
        cpu: "1m"
      limits:
        memory: "2Gi"
        cpu: "2"

I have mentioned stanza: pgbackrest as you can see but as soon as I create my first backup, stanza name is ignored and stanza is initialized with cluster name as you can see below in the log

{"level":"info","ts":"2025-07-26T20:59:20.960352193Z","msg":"Executing pgbackrest stanza-create command","logging_pod":"pg-test-cluster-1","options":["stanza-create","--repo1-type","s3","--repo1-s3-endpoint","xxx","--repo1-storage-verify-tls=n","--repo1-s3-bucket","pg-backup-01-prod","--repo1-path","/k8s-dbaas-test","--repo1-s3-uri-style","path","--pg1-path","/var/lib/postgresql/data/pgdata","--pg1-user","postgres","--pg1-socket-path","/controller/run/","--log-level-stderr","warn","--log-level-console","off","--stanza","pg-test-cluster","--lock-path","/controller/tmp/pgbackrest"]}

--stanza","pg-test-cluster" should be --stanza","pgbackrest" in my case

Thank you
frederic

[Agalin]

Thanks for reporting! Should be an easy fix. In the meantime you can create the stanza manually.

[dougkirkley]

@Agalin Have you had a chance at looking to fix this?

[dougkirkley]

I actually dug a little deeper and it seems the plugin configuration has a Stanza key that you can pass to the plugin and that is where the create stanza function gets the stanza from, instead of getting it from the archive object.

[Agalin]

So we have stanza configured in two places? I'd need to check logic to confirm when is each one used. Unfortunately we're really busy right now, feels like the busiest quarter I've seen in my company.

[dougkirkley]

@Agalin Yes, as far as I can tell the create stanza command uses a configuration from the plugin and the other commands seem to use a configuration from the Archive. If you want I can deprecate the plugin configuration in favor of only using the Archive as that makes more sense to me.

[Agalin]

Might not be so easy. Stanza selection in cluster's spec has its reasons - the same archive can be used for backups and WAL replication, you might also want to restore a backup from a different backup.

[dougkirkley]

That is fair, I did just use the configuration I'm the Cluster to restore from an old Crunchy postgres db stanza. As long as this is expected I don't see an issue here other than maybe to add in the Readme.