Repository navigation
test(stack-kms-vendor): share the vendor test harness and live workflow - #1556
Closed
freshtonic wants to merge 2 commits into
Closed
freshtonic wants to merge 2 commits into
freshtonic wants to merge 2 commits into
Conversation
Contributor
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: true |
🦋 Changeset detectedLatest commit: 3f1228c The changes in this PR will be included in the next version bump. This PR includes changesets to release 19 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Contributor
Mutation testing (cargo-mutants,
|
freshtonic
force-pushed
the
james/kms-vendor-test-harness
branch
from
November 9, 2026 04:16
d4ca39e to
3f1228c
Compare
freshtonic
force-pushed
the
james/kms-tests-vendor-key-name
branch
from
November 9, 2026 04:16
5a564a3 to
0e3e986
Compare
The fixture types, the fixture loader, body_json and the Replay transport were in each of the four vendor crates' tests/common/mod.rs. The copies were almost the same, but they had started to differ: only the Azure Replay kept its waits, and only the AWS copy sent a null body as "null". Move the harness to stack_kms_vendor::replay, behind the test-support feature. That feature already holds the contract suite and FakeVendor, which every vendor crate uses as a dev-dependency, so this needs no new crate and no new dependency edge. The module also holds the Recording transport that the Vault crate uses to write fixtures. Each tests/common/mod.rs now keeps only its vendor parts: the emulator, the test keys and the constants. The fixture files do not change. The feature now pulls in serde for the fixture types. The @cipherstash/auth binding does not turn on test-support, so its binary does not change. The changeset records the src/ change, as the repo rule requires.
integration-gcp-kms.yml and integration-azure-key-vault.yml had the same
job: a secret pre-flight, checkout, mise, the Rust cache and
mise run test:live:<crate>. Only the secrets were different.
Move that job to the reusable workflow _test-kms-live.yml. Each caller
keeps its triggers, its permissions, its concurrency group, and the job
id "live" with its name, its opt-in on the repository variable and its
fork-PR condition. So both stay inert until STACK_KMS_GCP_LIVE_KEY or
STACK_KMS_AZURE_LIVE_KEY is set, and the scans in
workflow-dispatch-job-conditions.test.mjs see the same jobs. The secret
names and the pre-flight messages do not change. The Google key still
goes to a file only the runner user can read, and the Azure secrets
still reach only the test step. Both path filters now include the shared
file.
The reusable workflow runs mise run test:live:${{ inputs.crate }}.
crates-ci.test.mjs read only the run lines of a workflow's own steps, so
it saw no caller for the two live tasks. It now reads the steps of a
reusable workflow in this repository through each job that calls it,
with the caller's inputs put in. A task counts for the caller, so
removing a caller still orphans its task.
freshtonic
force-pushed
the
james/kms-tests-vendor-key-name
branch
from
November 10, 2026 02:37
0e3e986 to
abf6a63
Compare
freshtonic
force-pushed
the
james/kms-vendor-test-harness
branch
from
November 10, 2026 02:37
3f1228c to
2d44caa
Compare
Contributor
Author
|
Folded into #1526 (the shared fixture harness, The plan is |
This was referenced Nov 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The four key vendor crates (AWS KMS, HashiCorp Vault, Google Cloud KMS, Azure Key Vault) each had their own copy of the same test harness: the fixture types, the fixture loader and a
Replaytransport that answers HTTP calls from recorded fixtures. The copies had started to differ. This PR moves the harness to one place. It also moves the job that the two opt-in live-test workflows had in common into one reusable workflow.No library behaviour changes.
Changes
stack-kms-vendor: newreplaymodule behind the existingtest-supportfeature (which already holds the contract suite andFakeVendor). No new crate.packages/stack-kms-{aws,vault,gcp,azure}/tests/common/mod.rs: keep only the vendor-specific parts (emulator, test keys, constants).Replaynow records the waits the client asks for (only Azure did before), and AWS sends anullfixture body as no bytes, as the other three did. No AWS fixture has a null body..github/workflows/_test-kms-live.yml: new reusable workflow.integration-gcp-kms.ymlandintegration-azure-key-vault.ymlcall it, and each keeps its triggers, permissions, concurrency, job id, opt-in variable and fork-PR condition.scripts/__tests__/crates-ci.test.mjs: it now follows a call to a reusable workflow in this repository, so it still finds the caller of eachtest:live:*task.AGENTS.md: notes on thereplaymodule and the new workflow.@cipherstash/authpatch, because code understack-kms-vendor/src/changed. The binding does not turn ontest-support, so its binary does not change.Verification
Run on the top branch of this stack (
james/kms-vendor-dispatch), on macOS:cargo fmt --all --checkandcargo clippy --workspace --all-features --all-targets -- -D warnings: pass.mise x --env test -- cargo nextest run --workspace --all-features: 1401 of 1402 pass. The one failure isstack-encrypt::ui derive_diagnostics(trybuild). It fails on every snapshot because of a local rustc wrapper that changes the paths in the compiler output. This stack does not touchstack-encrypt. CI is the check for it.mise run wasm:guest:test: 80 of 80 pass.go vet ./...andgo test -count=1 ./...inlanguages/golang: pass.pnpm --filter @cipherstash/auth test: 92 pass.pnpm --filter stash test: 1667 pass.cargo checkof the workspace and the guest (native andwasm32-wasip1) on each branch of the stack: pass.pnpm run test:scripts: pass.Review notes
<caller job name> / live. These jobs do nothing until a repository variable is set, so they should not be required checks. Please confirm that branch protection does not name them.Related
Refs #1541. Code-smell follow-up to the key vendor backend stack.