Skip to content

chore: use KMS-only SOPS encryption#14

Merged
xnoto merged 4 commits into
mainfrom
chore/add-sops-kms-recipient
Jun 19, 2026
Merged

chore: use KMS-only SOPS encryption#14
xnoto merged 4 commits into
mainfrom
chore/add-sops-kms-recipient

Conversation

@xnoto

@xnoto xnoto commented Jun 19, 2026

Copy link
Copy Markdown
Contributor

Summary

  • add the Make IT Work Cloud SOPS AWS KMS key as the SOPS recipient
  • remove the age recipient from .sops.yaml
  • re-key secrets/secrets.yaml so SOPS metadata is KMS-only
  • grant the caller workflow id-token: write for the shared workflow's GitHub OIDC role assumption
  • stop passing SOPS_AGE_KEY to the shared workflow

Dependency / rollout

  • Requires makeitworkcloud/tfroot-aws#6 and makeitworkcloud/shared-workflows#7, both now merged/applied.
  • makeitworkcloud/shared-workflows#8 removes the age secret from the reusable workflow itself.

Validation

  • AWS_PROFILE=makeitwork sops decrypt --output /dev/null secrets/secrets.yaml
  • verified SOPS metadata has kms=1 and age=0
  • PCT_TFPATH=$(command -v tofu) pre-commit run --all-files

@xnoto xnoto changed the title chore: add SOPS KMS recipient chore: use KMS-only SOPS encryption Jun 19, 2026
@github-actions

Copy link
Copy Markdown

OpenTofu Plan

No changes. Your infrastructure matches the configuration.

OpenTofu has compared your real infrastructure against your configuration and

@xnoto xnoto merged commit 11301ae into main Jun 19, 2026
3 checks passed
@xnoto xnoto deleted the chore/add-sops-kms-recipient branch June 19, 2026 04:31
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