coulomb/railiance-platform
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Record that both backup publisher slots are at version 2.
All checks were successful
CI Smoke / host-smoke (push) Successful in 1s
Details
CI Smoke / container-smoke (push) Successful in 2s
Details

Browse source 
The placeholders are gone. The bucket policy still names only the original backup application.

Assistant: grok
Assistant-Session: 01a11cdb-f9fe-7011-947c-936e72007e54
This commit is contained in:
codex 2026-10-08 23:19:21 +02:00
parent 31c679f212
commit dfb3e105fc
2 changed files with 62 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

6
workplans/RPF-WP-0053-coulomb-paired-backup-admission.md
View file

@ -230,9 +230,9 @@ remain open; no credentials delivered, productive capture/upload or timer enable
intended writer policy is `backup-pair-writer` and The founder admitted this writer on 2026-10-08, using the words
"bucket-pair-writer". The policy name remains `backup-pair-writer`
(`openbao/policies/backup-pair-writer.hcl`). The installed policy matches
that file, and `WRITER_ADMITTED` is true. Both backup-primary KV paths were absent. Version 1 now exists on each
path, with both field names set to a non-credential placeholder. The founder
will write the real pairs as a new UI version. The bootstrap key cannot list
that file, and `WRITER_ADMITTED` is true. Both backup-primary KV paths were absent. Version 2 is current on each path. Both pairs replaced the placeholder and
differ from each other. The values were not read out. The bucket policy still
has only the original three statements, so these keys cannot publish yet. The bootstrap key cannot list
IAM applications (403). The live bucket
policy still names only application ee80333e-5bab-4a04-85a9-5bdb46b7b3c1 on
`platform-pg/*`. No publisher key was created. T05 stays wait for the two