Skip to content

Usdk-e2e status check; testapp honors redisKeyPrefix - #175

Merged
bpapillon merged 3 commits into
mainfrom
sdk-e2e-status-check
Sep 6, 2026
Merged

Usdk-e2e status check; testapp honors redisKeyPrefix#175
bpapillon merged 3 commits into
mainfrom
sdk-e2e-status-check

Conversation

@bpapillon

@bpapillon bpapillon commented Sep 6, 2026

Copy link
Copy Markdown
Contributor

For the SDK E2E suite (SchematicHQ/actions#565):

  • sdk-e2e-status.yml posts an sdk-e2e commit status on every PR: pending on update-wasm-v* bump branches until the schematic-api E2E run reports back, success immediately on anything else. This lets sdk-e2e become a required check without blocking ordinary PRs.

  • The testapp honors redisKeyPrefix so the new replicator-docs E2E mode can run the README configuration.

  • redis_key_layout contract test: a copy of the replicator's key fixture (Redis key layout fixture as the SDK contract schematic-replicator#126); the Redis provider prefix plus the datastream key must reproduce the keys the replicator writes.

Posts an sdk-e2e commit status: pending on update-wasm-v* bump branches
until the schematic-api SDK E2E run reports back, success on every other
PR, so sdk-e2e can be a required check without blocking normal PRs. The
testapp passes redisKeyPrefix through so the E2E replicator-docs mode
runs the README configuration.
Copy of schematic-replicator/testdata/redis_key_layout.json; the Redis
provider prefix plus the datastream key must reproduce the keys the
replicator writes (SCH-7070).
@bpapillon
bpapillon marked this pull request as ready for review September 6, 2026 05:09
@bpapillon
bpapillon requested a review from a team as a code owner September 6, 2026 05:09
@bpapillon
bpapillon merged commit f10cb53 into main Sep 6, 2026
5 checks passed
@bpapillon
bpapillon deleted the sdk-e2e-status-check branch September 6, 2026 05:09
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.

2 participants