I5: Inventory and scope Actions secrets and service credentials #47

Open
opened 2026-11-09 17:06:00 +00:00 by claude · 2 comments
Member

claude can't see Actions secrets at repo or org level. Before CI does more, confirm what exists and that each credential has one purpose and the least access it needs.

Work (Eric): list secret names only, by repo and org, or give claude read access to names.
Work (Claude): map each one to its use; propose removals and splits. Details stay in the private assessment.

Acceptance: a names-only inventory exists privately. Unused secrets are removed. Shared credentials are split.

`claude` can't see Actions secrets at repo or org level. Before CI does more, confirm what exists and that each credential has one purpose and the least access it needs. **Work (Eric)**: list secret names only, by repo and org, or give `claude` read access to names. **Work (Claude)**: map each one to its use; propose removals and splits. Details stay in the private assessment. **Acceptance**: a names-only inventory exists privately. Unused secrets are removed. Shared credentials are split.
claude added this to the CI/CD 1: Runner policy and isolation milestone 2026-11-09 17:06:00 +00:00
claude added the cicdneeds-eric
priority
high
labels 2026-11-09 17:06:00 +00:00
claude added this to the CI/CD Roadmap project 2026-11-09 17:07:33 +00:00
Owner

No secrets have been configured in any repositories as of this time.

No secrets have been configured in any repositories as of this time.
Author
Member

Thanks. That settles the Actions half: there are no Actions secrets, so the inventory is empty and nothing needs removing. I've recorded that, with rules for adding the first ones, in docs/ci-cd/credentials.md (9b39c4a). One thing to confirm: did "any repositories" include org-level and user-level secrets (Site Administration, or each org's Settings → Actions → Secrets)? claude can't see those.

What's left is the service-credential half. In the Gitea role, one vault variable is used for more than one purpose. I've prepared the split without changing anything live:

  • DevOps/ansible-role-gitea@b5764c7 adds gitea_mailer_password and gitea_postgresql_password. Each defaults to the current value, so a role run with no new vault variables renders the same values as before. Bumped here in 9b39c4a.
  • docs/ci-cd/credentials.md maps each variable to its purpose and gives step-by-step rotation with rollback. The database step needs care: the PostgreSQL chart sets the password only when the database is first created, so it has to be changed in the database before the role runs.

Tested: a check playbook in a container (ansible-core 2.18) loads the role defaults with a stub admin value. The new variables resolve to the stub, and overriding them takes effect. yamllint and ansible-lint report nothing new beyond the role's existing indentation and line-length findings. Not tested: a real role run or a rotation.

For you (in this order, whenever convenient):

  1. Mailer: new password on the mailbox, then gitea_mailer_password in the vault, then ansible-playbook -i inventories/eom.dev.yml gitea.yaml. Gitea restarts for about a minute.
  2. Database: follow the PostgreSQL steps in the doc, after a backup.
  3. Then rotate gitea_admin_password itself.

There's one more related item for you, with details in the private assessment (finding 6). Please read it before step 1.

needs-eric stays until those are done and the org/user-level question is answered. Then I'll close this.

— eom-cicd-roadmap

Thanks. That settles the Actions half: **there are no Actions secrets, so the inventory is empty and nothing needs removing.** I've recorded that, with rules for adding the first ones, in `docs/ci-cd/credentials.md` (9b39c4a). One thing to confirm: did "any repositories" include **org-level and user-level** secrets (Site Administration, or each org's Settings → Actions → Secrets)? `claude` can't see those. **What's left is the service-credential half.** In the Gitea role, one vault variable is used for more than one purpose. I've prepared the split without changing anything live: - DevOps/ansible-role-gitea@b5764c7 adds `gitea_mailer_password` and `gitea_postgresql_password`. Each defaults to the current value, so a role run with no new vault variables renders the same values as before. Bumped here in 9b39c4a. - `docs/ci-cd/credentials.md` maps each variable to its purpose and gives step-by-step rotation with rollback. The database step needs care: the PostgreSQL chart sets the password only when the database is first created, so it has to be changed in the database before the role runs. **Tested:** a check playbook in a container (ansible-core 2.18) loads the role defaults with a stub admin value. The new variables resolve to the stub, and overriding them takes effect. `yamllint` and `ansible-lint` report nothing new beyond the role's existing indentation and line-length findings. **Not tested:** a real role run or a rotation. **For you (in this order, whenever convenient):** 1. Mailer: new password on the mailbox, then `gitea_mailer_password` in the vault, then `ansible-playbook -i inventories/eom.dev.yml gitea.yaml`. Gitea restarts for about a minute. 2. Database: follow the PostgreSQL steps in the doc, after a backup. 3. Then rotate `gitea_admin_password` itself. There's one more related item for you, with details in the private assessment (finding 6). Please read it before step 1. `needs-eric` stays until those are done and the org/user-level question is answered. Then I'll close this. — eom-cicd-roadmap
Sign in to join this conversation.
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DevOps/software-infrastructure#47