docs: record wave 3 in the README, CHANGELOG and conformance matrix - #161
Merged
Conversation
These were deliberately held back until the fixtures were proven, per the wave-3 brief: a row lands only after its fixture passes CRUD *and* discovery against a live subscription, never on the strength of a local run. Run 33818231073 came back 64 success / 2 skipped / 0 failures, so they land now. ## conformance-matrix.txt: +58 Nightly and CI share this file, so until now the 100 new resources had CI coverage (scoped by touched fixtures) and no nightly coverage at all. All 58 fixtures that passed that run are listed. The wave-3 fixtures NOT listed are in conformance-pr-skip.txt with the ARM error or structural reason inline. Three are called out in the file itself because no plugin change can fix them: automation-job-schedule (a jobScheduleId cannot be reused, and the harness re-applies one it deleted earlier in the run), api-management-service (ARM reports the update complete, then serves the previous publisherName) and avd-scaling-plan (needs the Azure Virtual Desktop service principal to hold host-pool read on the subscription). ## README: 173 -> 292 rows The table was missing 119 types, so it had fallen behind wave 2 as well as wave 3. Descriptions are the first sentence of each schema's own doc comment rather than freshly invented prose, trimmed at a clause boundary to the width the table already used; two that cut mid-clause were rewritten by hand, and AZURE::KeyVault::Key has no doc comment so its row was written directly. Registered types and README rows now both read 292, with nothing stale. ## CHANGELOG Per-namespace counts are taken from the types actually added in 80ebbd9, not estimated - my first draft had ApiManagement at 26, StreamAnalytics at 8 and DataProtection at 4, all wrong. Also records the two fixes worth knowing about from this wave: failure logging in pkg/prov/wrap.go, which had been discarding every ARM message, and the APIM purge in clean-environment.sh, which used a flag that does not exist and so had been failing silently while soft-deletes exhausted the Consumption cap. Gate: verify-schema, conformance-scope 13/13, reuse lint. Every matrix entry resolves to a fixture, no duplicates.
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.
Follow-up to #152. These rows were deliberately held back until the fixtures were
proven, per the wave-3 brief: a row lands only after its fixture passes CRUD and
discovery against a live subscription, never on the strength of a local run.
Run 33818231073
came back 64 success / 2 skipped / 0 failures, so they land now.
conformance-matrix.txt: +58Nightly and CI share this file. Until now the 100 new resources had CI coverage
(scoped by touched fixtures) and no nightly coverage at all.
The wave-3 fixtures not listed are in
conformance-pr-skip.txtwith the ARMerror or structural reason inline. Three are called out in the matrix itself
because no plugin change can fix them:
automation-job-schedulejobScheduleIdcannot be reused, and the harness re-applies one it deleted earlier in the runapi-management-servicepublisherNameavd-scaling-planThe first two would pass if the harness's OOB-delete phase recreated with a fresh
identity — worth raising with whoever owns it. The third needs a one-time role
assignment on the conformance subscription.
README: 173 → 292 rows
The table was missing 119 types, so it had fallen behind wave 2 as well as
wave 3. Descriptions are the first sentence of each schema's own doc comment
rather than freshly invented prose, trimmed at a clause boundary to the width the
table already used. Two that cut mid-clause were rewritten by hand, and
AZURE::KeyVault::Keyhas no doc comment so its row was written directly.Registered types and README rows now both read 292, with nothing stale.
CHANGELOG
Per-namespace counts are taken from the types actually added in
80ebbd9, notestimated — my first draft had ApiManagement at 26, StreamAnalytics at 8 and
DataProtection at 4, all wrong.
Verification
verify-schema,conformance-scope13/13, REUSE lintDocs only — no schema, provisioner or fixture changes.