coulomb/resource-control
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

retarget: T04 backup key is resource-control, not Barman

Browse source 
Handle becomes secret:railiance-platform/backup. IAM application is
resource-control; policy and API key are Scoped backup access.
This commit is contained in:
tegwick 2026-08-14 19:19:56 +02:00
parent 3241bace3c
commit 644d5391bd
5 changed files with 27 additions and 21 deletions
Download patch file Download diff file Expand all files Collapse all files

2
workplans/RESOURCE-WP-0006-resource-object-and-reef-refs.md
View file

@ -101,7 +101,7 @@ operational/credential refs or explicit gaps on every
`data/resources/` record. The proposed backup resource is the proving
case: consumers potential = `rapp-postgres`; actual = empty until WAL
flows; attribute refs wait on `reef-storage`; credential handle =
`secret:railiance-platform/platform-pg-backup-s3` once custody exists.
`secret:railiance-platform/backup` once custody exists.
Done when no live record relies on undifferentiated `workload_ids` as the
only consumer list.