Armando Ruocco 8b48609a82 fix: honor replica-source object store sidecar config for pg_basebackup replicas ... The sidecar injected into pg_basebackup replica clusters ignored the instanceSidecarConfiguration (resources, logLevel, additionalContainerArgs) of the replica-source ObjectStore: collectSidecarResourcesForPod and collectAdditionalInstanceArgs only handled the cluster and recovery object stores. Log-shipping replicas masked this because their recovery and replica source object stores coincide; pg_basebackup replicas only set ReplicaSourceBarmanObjectName, so the configuration was silently dropped (the sidecar ran with no additional args and the default log level). Handle ReplicaSourceBarmanObjectName in both helpers, documenting the store precedence (Barman > Recovery > ReplicaSource), and fix the misleading comment on the recovery branch. Signed-off-by: Armando Ruocco <armando.ruocco@enterprisedb.com>		2026-06-19 09:33:04 +02:00
..
common	fix: restore WAL from replica source during designated primary promotion (#966)	2026-06-18 18:14:33 +02:00
instance	fix(deps): update module sigs.k8s.io/controller-runtime to v0.24.0 (#880)	2026-05-06 10:15:29 +02:00
metadata	chore(main): release 0.13.0 (#860)	2026-06-10 10:55:17 +02:00
operator	fix: honor replica-source object store sidecar config for pg_basebackup replicas	2026-06-19 09:33:04 +02:00
restore	feat: pass additionalCommandArgs to barman-cloud-restore (#914)	2026-06-03 14:17:12 +02:00