mirror of
https://github.com/cozystack/cozystack.git
synced 2026-11-08 21:14:56 +09:00
Rewrite docs/agents/e2e-testing.md for the Chainsaw suite: declarative
asserts replace the until-get/wait backstops, Chainsaw cleanup replaces
test-level EXIT traps, catch blocks replace the `|| { ...; false; }` idiom,
and the TIA/diagnostics sections describe suites + `make test-chainsaw
CHAINSAW_SUITES`. Move the BATS->Chainsaw bullet out of 'in-flight' since it
is now the standard.
Fix references the migration left stale: hack/e2e-apps/ -> hack/e2e-chainsaw/
in the gemini styleguide and the nats/etcd backup READMEs. The
backup-postgres.bats / backup-foundationdb.bats files cited by the postgres
examples, the postgres README, and the foundationdb controller comment never
existed -- drop the false 'CI e2e drives this' claims and describe those
backup flows as the manual reference flows they are.
Assisted-By: Claude <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Signed-off-by: Myasnikov Daniil <myasnikovdaniil2001@gmail.com>
21 lines
849 B
YAML
21 lines
849 B
YAML
# Empty target Postgres instance for the to-copy restore. Keeping the spec
|
|
# minimal - the CNPG driver overlays bootstrap.* and backup.* values when
|
|
# the RestoreJob fires; the chart then renders externalClusters[] from
|
|
# those values so the new cluster's restore_command can fetch WALs from
|
|
# the source's S3 archive.
|
|
#
|
|
# This manifest is the reference for the same-namespace to-copy happy path:
|
|
# deploy it alongside pg-src and the restore leaves the source running. It
|
|
# is a manual / dev-cluster flow — the automated e2e suite (hack/e2e-chainsaw/)
|
|
# does not exercise postgres backups. The cross-tenant variant (target in
|
|
# tenant-test, source's seaweedfs in tenant-root) is blocked by the per-tenant
|
|
# Cilium egress policy.
|
|
---
|
|
apiVersion: apps.cozystack.io/v1alpha1
|
|
kind: Postgres
|
|
metadata:
|
|
name: pg-target
|
|
spec:
|
|
replicas: 2
|
|
size: 5Gi
|