Skip to content

feat(stack-kms-vault): HashiCorp Vault Transit key vendor backend (CIP-5310) - #1627

Draft
freshtonic wants to merge 1 commit into
james/cip-5307-stack-kms-awsfrom
james/cip-5310-stack-kms-vault
Draft

freshtonic wants to merge 1 commit into
james/cip-5307-stack-kms-awsfrom
james/cip-5310-stack-kms-vault

Conversation

@freshtonic

Copy link
Copy Markdown
Contributor

Layer 5 of the CIP-5203 stack. Implements CIP-5310.

  • New crate stack-kms-vault: a hand-written Transit client (encrypt, decrypt, rewrap).
  • stack_kms_vendor::bound binds the AAD into the wrapped key itself. Vault ignores context on a key that is not derived, and Azure (CIP-5309) needs the same mechanism.
  • Auth: token, AppRole, and Kubernetes (native only).
  • Tests: recorded fixtures, the contract suite, and a vault server -dev CI job.
  • The crate is staged in the stack-kms-vendor release group.

Decisions are in docs/plans/2026-11-05-key-vendor-backends-decisions.md (CIP-5310 sections).

@coderabbitai

coderabbitai Bot commented Nov 12, 2026

Copy link
Copy Markdown
Contributor

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

  • Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

@changeset-bot

changeset-bot Bot commented Nov 12, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: aeb384d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@github-actions

Copy link
Copy Markdown
Contributor

Mutation testing (cargo-mutants, --in-diff, stack-auth + stack-encrypt)

cargo-mutants did not complete (exit ) before producing results. Check the workflow run logs. The gate below will fail.

This branch has not been deployed

No deployments
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