retarget: T04 backup key is resource-control, not Barman
Handle becomes secret:railiance-platform/backup. IAM application is resource-control; policy and API key are Scoped backup access.
This commit is contained in:
parent
3241bace3c
commit
644d5391bd
5 changed files with 27 additions and 21 deletions
|
|
@ -67,7 +67,7 @@ secret:<custody_repo>/<secret_id>
|
|||
Example already named by the backup split:
|
||||
|
||||
```text
|
||||
secret:railiance-platform/platform-pg-backup-s3
|
||||
secret:railiance-platform/backup
|
||||
```
|
||||
|
||||
The handle may also record `broker` (`openbao`) and `rotation` as non-secret
|
||||
|
|
@ -92,9 +92,9 @@ When a record needs more than a string:
|
|||
{
|
||||
"kind": "credential_handle",
|
||||
"custody_repo": "railiance-platform",
|
||||
"secret_id": "platform-pg-backup-s3",
|
||||
"secret_id": "backup",
|
||||
"broker": "openbao",
|
||||
"ref": "secret:railiance-platform/platform-pg-backup-s3"
|
||||
"ref": "secret:railiance-platform/backup"
|
||||
}
|
||||
```
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue