feat(dw-demo-base): Invoke-DwPiiScan.ps1 - #96
Open
Justinvolved wants to merge 1 commit into
Open
Conversation
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
1 participant
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.
Wave-1 script 5 (4.28.0), stacked on the readiness PR. READ-ONLY, classes and counts only, never a value: string-column census (legacy ntext/text counted separately), person-PII counts on the platform tables, whole-database term sweep per -Term, rendered-page pass and anonymous-download probe by URL with locale-shaped -ShapePattern regexes. SQL sections local-only; hosted installs run the URL sections. pii-sweep.md names it as the enforced form of the mechanical steps — the rendered-page eyeball pass stays mandatory.
Verification: validator 0 errors, parses. Live smoke against a local demo DB: census (2384 columns/391 tables), person-PII counts matching the engagement's documented baseline shape, and the term sweep found real vendor residue the engagement's own sweep had missed (3 rows in a log table). The smoke also surfaced a module usage trap (@(call) double-wrap) now documented in Dw.Api.psm1's help on #92.