Refresh ProcessMapping drift canary: 10/78 → 13/89 - #16
Merged
Conversation
The live ui-insight/ProcessMapping repo's data/allowed_values.json grew to 13 controlled-value groups / 89 values (added CoverageAssertionMode, CoverageDepth, CoverageStatus, RedactionStatus, etc.). The drift canary still expected 10/78, so it failed on any PR that runs the drift workflow. Update the expectation to match the live registry.
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.
The live
ui-insight/ProcessMappingdata/allowed_values.jsonhas grown to 13 controlled-value groups / 89 values (new groups:CoverageAssertionMode,CoverageDepth,CoverageStatus,RedactionStatus, …), butscripts/check_governance_drift.pystill asserted the old10 / 78. That made the drift canary fail on every PR that runs the drift workflow — a latent failure, since no recent PR had touchedvendor/data-governancedownstream.Updates the expected counts to match the live registry. Pre-existing drift, unrelated to the concurrent
paused-status work.