Skip to content

security: codify GitHub WIF workflow allowlist - #1147

Open
think-back wants to merge 1 commit into
mainfrom
security/wif-workflow-allowlist-iac-20260909
Open

think-back wants to merge 1 commit into
mainfrom
security/wif-workflow-allowlist-iac-20260909

Conversation

@think-back

Copy link
Copy Markdown
Collaborator

Summary

  • map immutable GitHub repository and owner IDs plus workflow_ref into the shared deploy WIF provider
  • allow only the two staging deploy workflows on staging and the two production deploy workflows plus rollback on main
  • preserve the out-of-band rotated staging database password by ignoring Terraform password drift

Verification

  • terraform fmt -check -recursive deploy/gcp
  • terraform validate
  • targeted no-refresh plan: 0 add, 1 in-place provider update, 0 destroy
  • generated condition and new mappings exactly match the currently enforced live provider

Safety

  • no terraform apply was run
  • PR is not merged

Record the exact GitHub workflow trust boundary already enforced online and keep the rotated staging database password under out-of-band ownership.

Constraint: Trust must match immutable repository IDs and five exact workflow/ref pairs.

Rejected: Repository-name-only trust | It permits every workflow in the repository to impersonate the shared deployer.

Confidence: high

Scope-risk: narrow

Directive: Add any future deploy workflow and branch pair to allowed_workflows before expecting shared WIF authentication.

Tested: terraform fmt -check -recursive deploy/gcp; terraform validate; targeted plan showed 0 add, 1 update, 0 destroy; desired WIF condition and mappings match live.

Not-tested: terraform apply intentionally not run.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant