test: lock DB DevOps reuse field in bundled pipeline/template schemas - #825
Draft
cursor[bot] wants to merge 2 commits into
Draft
test: lock DB DevOps reuse field in bundled pipeline/template schemas#825cursor[bot] wants to merge 2 commits into
cursor[bot] wants to merge 2 commits into
Conversation
Add schema bundle contract assertions for the upstream reuse property on DB DevOps step definitions synced in chore/sync-schemas (#823). Co-authored-by: Rohan Gupta <thisrohangupta@users.noreply.github.com>
|
|
9 tasks
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.
Description
Adds schema bundle contract coverage for the upstream
reusefield introduced in the auto-sync harness schemas PR (#823).Triggered by: chore/sync-schemas (#823) — upstream added
reuseon DB DevOps step definitions (Flyway, Liquibase, DB schema apply/rollback, etc.). Without a contract test, a future sync or manual edit could drop the field silently whileharness_schemastill serves stale bundled YAML.Risky behavior now covered
reuseon seven DB DevOps step definitions in both v0pipelineandtemplatebundled schemasreuseaccepts literal strings (non-expression) vianot: { pattern: "^<\+.*>.*$" }reuseaccepts Harness input expressions (<+input>…) with the expected modifier vocabulary (allowedValues,selectOneFrom, andselectManyFromwhere upstream defines it)Test files added/updated
tests/schemas/schema-bundle-contract.test.tsWhy this reduces regression risk
harness_schemaand entity validation read these bundled snapshots; missingreusewould mislead agents authoring DB DevOps pipelinesType of Change
Checklist
pnpm testpasses (tests/schemas/schema-bundle-contract.test.ts)pnpm buildpassespnpm typecheckpassespnpm standards:checkpassespnpm docs:checkpasses (not applicable — no registry/tool count changes)Coding Standards (registry-driven MCP model)
Not applicable — test-only change.