Handle VNet JSON case-collision failures with Resource Graph fallback - #71
Handle VNet JSON case-collision failures with Resource Graph fallback#71mq-ssmith wants to merge 1 commit into
Conversation
|
mq-ssmith please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
|
|
Additional context for reviewers: This change addresses a real-world failure mode where VNet ARM payload parsing can fail due to case-colliding keys (example seen: This PR keeps the existing ARM path first, then uses a Resource Graph fallback for VNet inventory so collection can continue instead of failing hard. |
Summary\n- make dataCollectionVNets resilient when AzAPICall fails to parse mixed-case JSON keys\n- keep existing ARM call path first\n- add Resource Graph fallback (id,
ame, location, properties) when ARM parsing fails\n- continue collection for affected subscriptions instead of hard-skipping\n\n## Details\nThis addresses the real-world payload case where key casing collisions (for example Environment vs �nvironment) can break JSON conversion in the VNet ARM response.\n\n## Files changed\n- pwsh/AzGovVizParallel.ps1\n- pwsh/dev/functions/dataCollection/dataCollectionFunctions.ps1\n\n## Validation\n- PowerShell parser diagnostics report no errors in changed files\n- change is scoped to VNet collection only