Skip to content

test(stack-kms-azure): name the fixture AES key the vendor key - #1555

Draft
freshtonic wants to merge 1 commit into
james/cip-5313-document-key-vendor-backend-trade-offs-capability-matrixfrom
james/kms-tests-vendor-key-name
Draft

freshtonic wants to merge 1 commit into
james/cip-5313-document-key-vendor-backend-trade-offs-capability-matrixfrom
james/kms-tests-vendor-key-name

Conversation

@freshtonic

Copy link
Copy Markdown
Contributor

Summary

Test-only rename. The Azure Key Vault emulator in the tests called its AES wrapping key a "KEK". The project glossary (packages/stack-encrypt/CONTEXT.md) lists KEK as a term to avoid, because in this design the vendor key is the key that wraps. No behaviour changes.

Changes

  • packages/stack-kms-azure/tests: TEST_ONLY_KEK is now TEST_ONLY_VENDOR_KEY, and the kek parameters are vendor_key.

Verification

  • mise x --env test -- cargo nextest run -p stack-kms-azure --all-features: 57 of 57 pass.
  • cargo clippy -p stack-kms-azure --all-features --all-targets -- -D warnings and cargo fmt --check: pass.

Related

Refs #1541 (the PR below this one in the stack). Code-smell follow-up to the key vendor backend stack.

The emulator's AES key-wrap helpers called the key a KEK. CONTEXT.md lists
KEK as a term to avoid: the vendor key is the key that wraps. Rename
TEST_ONLY_KEK to TEST_ONLY_VENDOR_KEY and the kek parameters to vendor_key.
@changeset-bot

changeset-bot Bot commented Nov 6, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 5a564a3

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

@coderabbitai

coderabbitai Bot commented Nov 6, 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

@freshtonic
freshtonic added this pull request to stack #1523 November 6, 2026 11:25

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