AzLocal.UpdateManagement v0.8.73 - cycle calendar inline cluster counts#79
Merged
Conversation
…e-triggers marker (GH+ADO) The schedule-triggers AZLOCAL-CUSTOMIZE marker wrapped ~30 lines of author guidance (incl. the New-AzLocalApplyUpdatesScheduleConfig -OutputPath example and the default-path note). Update-AzLocalPipelineExample preserves the marker BODY from the customer's file, so author corrections inside the marker (e.g. the v0.8.71 .github -> config path fix) never reach an already-deployed consumer. Moved all guidance above the BEGIN marker; marker body now holds only the trigger directive (GH placeholder comment / ADO 'trigger: none'). Queued for next version bump.
…Step.0 -> Step.00 ... Step.9 -> Step.09) Queued for 0.8.72 (no version bump). The GitHub Actions sidebar and ADO pipelines list sort workflows alphabetically by their display name, so Step.10 lexically sorted between Step.1 and Step.2. Zero-padding the single-digit step numbers makes Step.10 sort last as intended. Scope (display/title text only, fully reversible): - GitHub Actions workflow `name:` fields (10 files; Step.10 unchanged) - Azure DevOps `name:` / stage `displayName:` Step.N labels - Header-comment titles (`# Step.N - ...`) on both platforms - One ADO "HOW TO RUN" prose line tracking its renamed display name Left unchanged: artifact names (azlocal-step.N-* functional identifiers) and cross-reference prose (e.g. "Step.9 / Step.10 wiring").
Patch release. No module code, API, or export-count change (60 exports). Bundles the two pipeline-template improvements committed on this branch since v0.8.71: Fixed - apply-updates.yml (GH + ADO): moved the schedule-path author guidance (incl. the New-AzLocalApplyUpdatesScheduleConfig -OutputPath example and the default-path note) OUTSIDE the schedule-triggers AZLOCAL-CUSTOMIZE marker. Update-AzLocalPipelineExample preserves the marker body from the customer's file, so guidance corrections inside the marker never reached already-deployed consumers. Guidance now lives above the BEGIN marker. Changed - Zero-padded single-digit Step.N pipeline display names to two digits (Step.0 -> Step.00 ... Step.9 -> Step.09) so Step.10 sorts last in the GitHub Actions sidebar / Azure DevOps pipelines list. Display/title text only; artifact names and cross-reference prose unchanged. - Bumped GENERATED_AGAINST_MODULE_VERSION pins 0.8.71 -> 0.8.72 across all bundled pipeline YAMLs. Version bump applied to psd1/psm1/CHANGELOG/README/Tests/docs.
…s inline into Eligible rings column - Get-AzLocalApplyUpdatesScheduleCycleCalendar: when -ClusterRingCounts is supplied, relabel the "Eligible rings" header to "Eligible rings (cluster count)" and append each ring's count inline (e.g. `Prod` (9), `Canary` (3)); removed the separate "Clusters in ring(s)" column. Per-ring projection table (-IncludePerRingSummary) keeps its standalone "Cluster count" column. - Export-AzLocalApplyUpdatesScheduleAudit: build a ring -> tagged-cluster-count map from the cluster CSV and forward it to the cycle-calendar cmdlet (the Step.3 render path never passed it before, so inline counts were silently absent from production output). - Tests: updated header/cell assertions for the inline format; added a TOC regression guard that the README lists exactly one top-level "What's New" entry (current release only). - README TOC: removed stale "What's New in v0.8.7" / "v0.8.4" entries; prior versions live under Release History. - Version bump 0.8.72 -> 0.8.73 across psd1/psm1/CHANGELOG/README/tests/docs and all bundled pipeline YAML GENERATED_AGAINST_MODULE_VERSION pins.
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
AzLocal.UpdateManagementv0.8.73 - cycle-calendar refinement for the Step.3 apply-updates schedule audit. Per-ring cluster counts now render INLINE in the "Eligible rings" column, and the Step.3 pipeline render path actually populates them. No public API or export-count change (still 60 cmdlets).Changes
Get-AzLocalApplyUpdatesScheduleCycleCalendar: when-ClusterRingCountsis supplied, the per-day calendar relabels the headerEligible rings->Eligible rings (cluster count)and appends each ring's count inline to its token, e.g.`Prod` (9), `Canary` (3). The separate "Clusters in ring(s)" column is removed. Dead days still render_(none - dead day)_. The per-ring projection table (-IncludePerRingSummary) keeps its standalone "Cluster count" column.Export-AzLocalApplyUpdatesScheduleAudit(the cmdlet the Step.3apply-updates-schedule-auditpipeline calls): now builds a ring -> tagged-cluster-count map from the supplied cluster CSV and forwards it to the cycle-calendar cmdlet. Previously it never forwarded-ClusterRingCounts, so the cluster-count enrichment was silently absent from every rendered Step.3 summary.Tests
v0.8.7/v0.8.4TOC links survive earlier bumps.Versioning
0.8.72->0.8.73across psd1/psm1/CHANGELOG/README/tests/docs and all bundled pipeline YAMLGENERATED_AGAINST_MODULE_VERSIONpins.What's New in v0.8.7/v0.8.4TOC entries from the README.