chore(reports): regenerate reports/capability map for REST 2.28 - #61
Merged
juemerson-at-purestorage merged 1 commit intoJul 27, 2026
Conversation
…ap, and field-cmdlet map
Data/PfbCapabilityMap.json, Reports/PfbApiDriftReport.{json,md},
Reports/PfbValueEnumMap.json, Reports/PfbValueEnumReconciliation.md, and
Reports/PfbFieldCmdletMap.{json,md} were stale relative to both PR dmann000#60 (drift
report enrichment/confidence work) and REST 2.28, which had already been
fetched into the local tools/specs/ cache but never folded into these
committed artifacts. Regenerated all four via their tools/Build-Pfb*.ps1
scripts against the current 29-version spec cache -- no manual edits.
Notable deltas: capability map now spans 2.0-2.28 (632 endpoints); drift
report gaps grew modestly (432->433 endpoints, 605->609 addable body props,
1002->1004 query params, 1 new ValidateSet candidate); field-cmdlet map goes
from matched:0 to matched:1 (Get-PfbPolicyAllMember -MemberType) with
not-found-in-resource 2->3 -- the full 4-candidate population of typed
parameters with any spec-documented enum at all, confirming the
2026-07-27 field-cmdlet-map-resource-hint-design.md finding that a better
resource hint can't move the remaining no-spec-enum-found candidates.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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.
Summary
Data/PfbCapabilityMap.json,Reports/PfbApiDriftReport.{json,md},Reports/PfbValueEnumMap.json,Reports/PfbValueEnumReconciliation.md, andReports/PfbFieldCmdletMap.{json,md}were stale relative to both Drift Report enhancements: per-parameter confidence, enrichment, systemic gaps, annotations #60 (drift report enrichment/confidence work) and REST 2.28, which had already been fetched into the localtools/specs/cache but never folded into these committed artifacts.tools/Build-Pfb*.ps1scripts against the current 29-version spec cache (2.0-2.28). No manual edits, notools//Public/code changes.matched: 0tomatched: 1(Get-PfbPolicyAllMember -MemberType) withnot-found-in-resource2->3 -- the full population of typed parameters with any spec-documented enum at all.Test plan
tools/Build-PfbCapabilityMap.ps1,tools/Build-PfbApiDriftReport.ps1,tools/Build-PfbValueEnumMap.ps1,tools/Build-PfbFieldCmdletMap.ps1locally against the cached specs and committed their output verbatim.Public/cmdlet ortools/lib/*.ps1logic touched, so no live-array testing applies.🤖 Generated with Claude Code