v0.8.3: Step.3 apply-updates schedule-coverage advisor accuracy fixes#72
Merged
Conversation
- Recommend view (Test-AzLocalApplyUpdatesScheduleCoverage): when -PipelineYamlPath is supplied, diff-prune recommended crons against the schedule-bearing yml so operators no longer see steady-state crons re-emitted as 'add me' suggestions. - Step.3 yml (GH + ADO): pipeline_path / pipelinePath input is now REQUIRED. Empty value throws at runtime instead of silently falling through to schedule-only mode. - Step.3 Allow-list section heading reframed from misleading 'How to fix - edit $schedulePath' to 'Optional - pin a ring to a specific update in $schedulePath', with disclaimer that it is NOT a fix for cron-coverage or ring-diff sections above. - Step.3 yml: closing-fence typo (6 backticks + n) corrected to 7 backticks + n at 4 sites across GH+ADO. - All 20 Step.*.yml templates: GENERATED_AGAINST_MODULE_VERSION pinned to 0.8.3. - Pester: drift test bumped, Allow-list heading-shape test rewritten, 3 new diff-prune Context tests added (829 passed, 0 failed, 1 skipped). - README + docs/release-history.md + CHANGELOG.md + psd1 ReleaseNotes updated; v0.8.2 demoted to Release History; ReleaseNotes trimmed to 8316 chars (under PSGallery 10000 limit).
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.
AzLocal.UpdateManagement v0.8.3 — Step.3 advisor accuracy fixes
Ships four defect fixes for the apply-updates schedule-coverage advisor (Step.3) and the underlying
Test-AzLocalApplyUpdatesScheduleCoveragecmdlet.Fixes
Recommend view diff-prunes against
-PipelineYamlPathWhen
-PipelineYamlPathis supplied,Test-AzLocalApplyUpdatesScheduleCoverage -View Recommendnow removes recommended crons that are already present (and valid) in the schedule-bearing yml. Previously operators copy-pasted steady-state crons back into the schedule, creating duplicates.Step.3 yml
pipeline_path/pipelinePathis now REQUIREDGH input gets
required: true. ADOparameters:blocks gain an explicitthrowfor empty string at the start of each script. Eliminates silent fall-through to schedule-only mode.Allow-list heading reframed + disclaimer
Old (misleading):
### How to fix - edit \New:
### Optional - pin a ring to a specific update in \plusThis is NOT a fix for the cron-coverage or ring-diff sections above.Closing-fence typo
\\\\\\(6 backticks + n, four sites across GH+ADO Step.3 yml) →\\\\\\\(7 backticks + n). Markdown code-fence terminator was eating the next paragraph in some renderers.Other
Step.*.ymltemplates:GENERATED_AGAINST_MODULE_VERSIONbumped to0.8.3.ModuleVersion = '0.8.3'in psd1 +\in psm1.ReleaseNotes(PSData): v0.8.3 entry prepended; v0.8.2 trimmed to a one-line summary + CHANGELOG link so ReleaseNotes stays under PSGallery's 10000-char ceiling (current: 8316 chars).README.md/docs/release-history.md/CHANGELOG.md: v0.8.3 documented; v0.8.2 demoted to Release History.Tests
0.8.3.[GitHub, ADO].Context 'v0.8.3 - Recommend diff-prunes crons already present in -PipelineYamlPath'block: 3Itblocks covering (a) full prune when all recommended crons already present, (b) back-compat when-PipelineYamlPathomitted, (c) partial prune when only one of two recommended crons is already present.