test(clickhouse): list the system-bucket round-trip in the suite header

The header names the backup Tests of the suite and why they are split;
it still described two of them after the third was added, so a reader
starting from it would miss the only Test that covers the system-bucket
path.

Assisted-by: LLM
Signed-off-by: Alexey Artamonov <aleksei.artamonov@aenix.io>
This commit is contained in:
Alexey Artamonov committed 2026-11-11 14:56:26 +03:00
1 parent 8ba0380043
commit 35823c6c9c
1 file changed
+9 -2
@@ -91,7 +91,7 @@ spec:
status:
replicas: 1
---
# ClickHouse Altinity backup/restore E2E — the two backup Tests below sit in
# ClickHouse Altinity backup/restore E2E — the three backup Tests below sit in
# this suite alongside the plain `clickhouse` Test above. Chainsaw port of the
# intended hack/e2e-apps/backup-clickhouse.bats (cozystack#2600), shaped like the
# etcd/mariadb/postgres suites:
@@ -107,8 +107,15 @@ spec:
# driving the validated example scripts
# (examples/backups/clickhouse). Also runs in
# CI, in tenant-root.
# clickhouse-3-system-bucket-roundtrip
# — backup and in-place restore through the
# shipped cozy-default BackupClass and the
# platform system bucket, for a release
# whose Pod started before its credentials
# were projected. Runs in CI, in tenant-root.
#
# Why the split: the two Tests answer different questions at different cost. The
# Why the split: the first two Tests answer different questions at different
# cost, and the third covers the system-bucket path neither of them takes. The
# contracts Test needs no object store, so it stays in the default tenant-test
# namespace next to the other app suites and is the seconds-long guard on the
# chart wiring the Altinity strategy depends on — the sidecar container/port and