WAL arhives uploaded always, ignoring isWALArchiver setting

[dragoangel]

If user will omit or configure isWALArchiver=false inside cluster CR - barman-cloud plugin will still upload WAL to S3.

Steps done:
Tried omitting isWALArchiver:

    plugins:
      - name: barman-cloud.cloudnative-pg.io
        enabled: true
        parameters:
          barmanObjectName: cnpg-cluster-01-backup

and setting it to false:

    plugins:
      - name: barman-cloud.cloudnative-pg.io
        enabled: true
        isWALArchiver: false
        parameters:
          barmanObjectName: cnpg-cluster-01-backup

Expected result: no wal folder would be created
Actual result: cnpg-cluster-01-backup S3 object get wal folder and files inside after cluster creation

[dosubot]

The barman-cloud plugin currently ignores the isWALArchiver setting—WAL files are always uploaded to S3, even if you set isWALArchiver: false or omit it. This matches both the code and documentation, which do not implement logic to disable WAL archiving based on this setting. The documentation only describes enabling WAL archiving by setting isWALArchiver: true, but does not mention disabling it by setting it to false or omitting it. So, the behavior you’re seeing is expected with the current implementation. Reference

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}