AzLocal.UpdateManagement v0.8.72 - pipeline-template polish (patch) (#78)

* apply-updates.yml: move schedule-path author guidance OUTSIDE schedule-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.

* pipelines: zero-pad single-digit Step.N display names to two digits (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").

* AzLocal.UpdateManagement v0.8.72 - pipeline-template polish (patch)

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.

* tests: record v0.8.72 wall-clock timing row (1145 tests, 96.82s wall, 0 failed)

Author: NeilBird

AzLocal.UpdateManagement/Automation-Pipeline-Examples/azure-devops/apply-updates-schedule-audit.yml

@@ -1,5 +1,5 @@
 # AZLOCAL-PIPELINE-ID: apply-updates-schedule-audit
-# Step.3 - Apply-Updates Schedule Coverage Audit Pipeline
+# Step.03 - Apply-Updates Schedule Coverage Audit Pipeline
 # This pipeline runs the read-only Test-AzLocalApplyUpdatesScheduleCoverage advisor
 # weekly to detect drift between the cron schedule(s) in your apply-updates pipeline
 # YAML and the UpdateStartWindow tags that operators have placed on Azure Local clusters.
@@ -87,7 +87,7 @@ parameters:
     default: false
 
 variables:
-  GENERATED_AGAINST_MODULE_VERSION: '0.8.71'
+  GENERATED_AGAINST_MODULE_VERSION: '0.8.72'
   REQUIRED_MODULE_VERSION: '${{ parameters.moduleVersion }}'
   reportsPath: '$(Build.ArtifactStagingDirectory)/reports'
   # v0.8.7 sideload advisor defaults. Override at the pipeline / variable-group

AzLocal.UpdateManagement/Automation-Pipeline-Examples/azure-devops/apply-updates.yml

@@ -1,8 +1,11 @@
 # AZLOCAL-PIPELINE-ID: apply-updates
-# Step.7 - Apply Updates to Azure Local Clusters
+# Step.07 - Apply Updates to Azure Local Clusters
 # This pipeline applies updates to clusters filtered by UpdateRing tag value
 
-# BEGIN-AZLOCAL-CUSTOMIZE:schedule-triggers
+# Author guidance lives OUTSIDE the customise markers so module refreshes
+# (Update-AzLocalPipelineExample) can correct it; only the trigger directive
+# between the markers is preserved verbatim across module upgrades.
+#
 # PREFERRED PATTERN - drive automated update runs from a ring-aware
 # schedule file (config/apply-updates-schedule.yml by default),
 # not from per-window crons.
@@ -39,8 +42,10 @@
 #         include: [main]
 #       always: true
 #
-# Content between BEGIN/END markers is preserved by
-# Update-AzLocalPipelineExample across module upgrades.
+# Replace `trigger: none` between the BEGIN/END markers below with your
+# schedules: block. That region (and ONLY that region) is preserved verbatim
+# by Update-AzLocalPipelineExample across module upgrades.
+# BEGIN-AZLOCAL-CUSTOMIZE:schedule-triggers
 trigger: none
 # END-AZLOCAL-CUSTOMIZE:schedule-triggers
 
@@ -115,7 +120,7 @@ variables:
   # log if the YAML appears stale - prompting you to refresh via
   # Copy-AzLocalPipelineExample -Update. See Automation-Pipeline-Examples/README.md section 5.
   - name: GENERATED_AGAINST_MODULE_VERSION
-    value: '0.8.71'
+    value: '0.8.72'
   # Resolution order for the module version pin (leave all unset to install the latest,
   # which is the default "fix-forward" behaviour): queue-time parameter > pipeline variable
   # 'REQUIRED_MODULE_VERSION' overridden at queue time > empty (latest).

AzLocal.UpdateManagement/Automation-Pipeline-Examples/azure-devops/assess-update-readiness.yml

@@ -1,5 +1,5 @@
 # AZLOCAL-PIPELINE-ID: assess-update-readiness
-# Step.5 - Assess Update Readiness (Pre-flight go/no-go gate)
+# Step.05 - Assess Update Readiness (Pre-flight go/no-go gate)
 # --------------------------------------------------
 # Runs Get-AzLocalClusterUpdateReadiness and Test-AzLocalClusterHealth -BlockingOnly
 # against a target UpdateRing (or the whole fleet) BEFORE apply-updates.yml runs.
@@ -70,7 +70,7 @@ variables:
   # the version actually installed and to the latest on PSGallery, and emits a warning
   # log if the YAML appears stale - prompting you to refresh via
   # Copy-AzLocalPipelineExample -Update. See Automation-Pipeline-Examples/README.md section 5.
-  GENERATED_AGAINST_MODULE_VERSION: '0.8.71'
+  GENERATED_AGAINST_MODULE_VERSION: '0.8.72'
   # Resolution order for the module version pin (leave all unset to install the latest,
   # which is the default "fix-forward" behaviour): queue-time parameter > pipeline variable
   # 'REQUIRED_MODULE_VERSION' overridden at queue time > empty (latest).

AzLocal.UpdateManagement/Automation-Pipeline-Examples/azure-devops/authentication-test.yml

@@ -1,5 +1,5 @@
 # AZLOCAL-PIPELINE-ID: authentication-test
-# Step.0 - Authentication Validation and Subscription Scope Report
+# Step.00 - Authentication Validation and Subscription Scope Report
 #
 # PURPOSE:
 #   Validates that the service connection (Workload Identity Federation), App Registration,
@@ -35,11 +35,11 @@
 #   - Pipeline artifact (auth-report) containing JUnit XML + subscriptions.json + .csv.
 #
 # HOW TO RUN (after the file is committed and the pipeline is imported):
-#   Pipelines -> Step.0 - Authentication Validation and Subscription Scope Report -> Run pipeline.
+#   Pipelines -> Step.00 - Authentication Validation and Subscription Scope Report -> Run pipeline.
 #
 # See Automation-Pipeline-Examples/README.md, section 5.2, for the full setup story.
 
-name: Step.0 - Authentication Validation and Subscription Scope Report
+name: Step.00 - Authentication Validation and Subscription Scope Report
 
 # BEGIN-AZLOCAL-CUSTOMIZE:schedule-triggers
 # Add or modify `schedules:` blocks here to enable cron-driven runs. Content
@@ -60,7 +60,7 @@ variables:
   # log if the YAML appears stale - prompting you to refresh via
   # Copy-AzLocalPipelineExample -Update. See Automation-Pipeline-Examples/README.md section 5.
   - name: GENERATED_AGAINST_MODULE_VERSION
-    value: '0.8.71'
+    value: '0.8.72'
   # Resolution order for the module version pin (leave all unset to install the latest,
   # which is the default "fix-forward" behaviour): queue-time parameter > pipeline variable
   # 'REQUIRED_MODULE_VERSION' overridden at queue time > empty (latest).

AzLocal.UpdateManagement/Automation-Pipeline-Examples/azure-devops/fleet-connectivity-status.yml

@@ -1,5 +1,5 @@
 # AZLOCAL-PIPELINE-ID: fleet-connectivity-status
-# Step.4 - Fleet Connectivity Status Monitoring Pipeline
+# Step.04 - Fleet Connectivity Status Monitoring Pipeline
 # This pipeline surfaces network-connectivity issues across every Azure Local
 # cluster the service connection can read - four scopes in one pipeline:
 #
@@ -49,7 +49,7 @@
 
 # Pipeline display name carries the same Step.N - prefix as the filename so the
 # ADO pipelines list (sorts by `name:` field) lists pipelines in execution order.
-name: Step.4 - Fleet Connectivity Status
+name: Step.04 - Fleet Connectivity Status
 
 # BEGIN-AZLOCAL-CUSTOMIZE:schedule-triggers
 # Edits inside this block are preserved across Update-AzLocalPipelineExample
@@ -110,7 +110,7 @@ variables:
   # the version actually installed and to the latest on PSGallery, and emits a warning
   # log if the YAML appears stale - prompting you to refresh via
   # Copy-AzLocalPipelineExample -Update. See Automation-Pipeline-Examples/README.md section 5.
-  GENERATED_AGAINST_MODULE_VERSION: '0.8.71'
+  GENERATED_AGAINST_MODULE_VERSION: '0.8.72'
   # Resolution order for the module version pin (leave all unset to install the latest,
   # which is the default "fix-forward" behaviour): queue-time parameter > pipeline variable
   # 'REQUIRED_MODULE_VERSION' overridden at queue time > empty (latest).

AzLocal.UpdateManagement/Automation-Pipeline-Examples/azure-devops/fleet-health-status.yml

@@ -105,7 +105,7 @@ variables:
   # the version actually installed and to the latest on PSGallery, and emits a warning
   # log if the YAML appears stale - prompting you to refresh via
   # Copy-AzLocalPipelineExample -Update. See Automation-Pipeline-Examples/README.md section 5.
-  GENERATED_AGAINST_MODULE_VERSION: '0.8.71'
+  GENERATED_AGAINST_MODULE_VERSION: '0.8.72'
   # Resolution order for the module version pin (leave all unset to install the latest,
   # which is the default "fix-forward" behaviour): queue-time parameter > pipeline variable
   # 'REQUIRED_MODULE_VERSION' overridden at queue time > empty (latest).

AzLocal.UpdateManagement/Automation-Pipeline-Examples/azure-devops/fleet-update-status.yml

@@ -1,5 +1,5 @@
 # AZLOCAL-PIPELINE-ID: fleet-update-status
-# Step.9 - Fleet Update Status Monitoring Pipeline
+# Step.09 - Fleet Update Status Monitoring Pipeline
 # This pipeline monitors update status across all Azure Local clusters and generates reports
 #
 # USE CASES:
@@ -93,7 +93,7 @@ variables:
   # the version actually installed and to the latest on PSGallery, and emits a warning
   # log if the YAML appears stale - prompting you to refresh via
   # Copy-AzLocalPipelineExample -Update. See Automation-Pipeline-Examples/README.md section 5.
-  GENERATED_AGAINST_MODULE_VERSION: '0.8.71'
+  GENERATED_AGAINST_MODULE_VERSION: '0.8.72'
   # Resolution order for the module version pin (leave all unset to install the latest,
   # which is the default "fix-forward" behaviour): queue-time parameter > pipeline variable
   # 'REQUIRED_MODULE_VERSION' overridden at queue time > empty (latest).

AzLocal.UpdateManagement/Automation-Pipeline-Examples/azure-devops/inventory-clusters.yml

@@ -1,5 +1,5 @@
 # AZLOCAL-PIPELINE-ID: inventory-clusters
-# Step.1 - Inventory Azure Local Clusters
+# Step.01 - Inventory Azure Local Clusters
 # This pipeline queries all Azure Local clusters and exports inventory with UpdateRing tag status
 #
 # OUTPUT COLUMNS:
@@ -43,7 +43,7 @@ variables:
   # log if the YAML appears stale - prompting you to refresh via
   # Copy-AzLocalPipelineExample -Update. See Automation-Pipeline-Examples/README.md section 5.
   - name: GENERATED_AGAINST_MODULE_VERSION
-    value: '0.8.71'
+    value: '0.8.72'
   # Resolution order for the module version pin (leave all unset to install the latest,
   # which is the default "fix-forward" behaviour): queue-time parameter > pipeline variable
   # 'REQUIRED_MODULE_VERSION' overridden at queue time > empty (latest).

AzLocal.UpdateManagement/Automation-Pipeline-Examples/azure-devops/manage-updatering-tags.yml

@@ -1,5 +1,5 @@
 # AZLOCAL-PIPELINE-ID: manage-updatering-tags
-# Step.2 - Manage UpdateRing Tags
+# Step.02 - Manage UpdateRing Tags
 # This pipeline creates or updates UpdateRing tags on Azure Local clusters from a CSV file
 #
 # WORKFLOW:
@@ -46,7 +46,7 @@ variables:
   # log if the YAML appears stale - prompting you to refresh via
   # Copy-AzLocalPipelineExample -Update. See Automation-Pipeline-Examples/README.md section 5.
   - name: GENERATED_AGAINST_MODULE_VERSION
-    value: '0.8.71'
+    value: '0.8.72'
   # Resolution order for the module version pin (leave all unset to install the latest,
   # which is the default "fix-forward" behaviour): queue-time parameter > pipeline variable
   # 'REQUIRED_MODULE_VERSION' overridden at queue time > empty (latest).

AzLocal.UpdateManagement/Automation-Pipeline-Examples/azure-devops/monitor-updates.yml

@@ -1,5 +1,5 @@
 # AZLOCAL-PIPELINE-ID: monitor-updates
-# Step.8 - Monitor In-Flight Updates (Azure DevOps)
+# Step.08 - Monitor In-Flight Updates (Azure DevOps)
 # -----------------------------------------------------------
 # Reports clusters whose latest update run is currently in flight, with the
 # CURRENT STEP each cluster is on and the ELAPSED DURATION of the run. Built
@@ -84,7 +84,7 @@ parameters:
     default: ''
 
 variables:
-  GENERATED_AGAINST_MODULE_VERSION: '0.8.71'
+  GENERATED_AGAINST_MODULE_VERSION: '0.8.72'
   REQUIRED_MODULE_VERSION: '${{ parameters.moduleVersion }}'
   reportsPath: '$(Build.ArtifactStagingDirectory)/reports'