Files
Alexey Artamonov f02ca8cbc2 test(backups): log in as an application user after each restore
The backup examples and e2e suites no longer set passwords. They read
the generated ones from <release>-credentials with jq, since a username
may contain a dot that jsonpath treats as a path step, and log in as an
application user after each restore, so a restore that leaves the
credentials unusable fails the run. The MariaDB run also checks that an
account created out of band on the source is absent from the copy. The
unreachable-target restore step asserts a terminal Failed attributed to
the recovery window, since the reason itself is best effort.

Signed-off-by: Alexey Artamonov <aleksei.artamonov@aenix.io>
2026-09-24 18:11:07 +03:00

33 lines
673 B
YAML

apiVersion: apps.cozystack.io/v1alpha1
kind: Postgres
metadata:
name: test
spec:
external: false
size: 10Gi
replicas: 2
storageClass: ""
postgresql:
parameters:
max_connections: "100"
quorum:
minSyncReplicas: 0
maxSyncReplicas: 0
users:
testuser: {}
databases:
testdb:
roles:
admin:
- testuser
backup:
enabled: false
destinationPath: s3://postgres-backups/pg/
endpointURL: https://s3.example.org
retentionPolicy: "30d"
schedule: "0 0 2 * * *"
s3AccessKey: oobaiRus9pah8PhohL1ThaeTa4UVa7gu
s3SecretKey: ju3eum4dekeich9ahM1te8waeGai0oog
resources: {}
resourcesPreset: "nano"