v0.8.87: pipeline display-name rename (Config/Monitor/Update) + connectivity output + monitor ITSM (#93)

* v0.8.85: consolidate setup workflow and align pipeline/version metadata

* test-run-timings

* v0.8.85 follow-up: delete ADO auth+inventory workflows and add merged ADO setup pipeline

* v0.8.85 follow-up: move collapsible subscription section into Export-AzLocalAuthValidationReport cmdlet; track test-run-timings.csv

* v0.8.85 follow-up: fix live integration test failures (Step.0 ErrorActionPreference, Step.3 path, Step.4 SummaryPath)

* Add test-run-timings.csv to repo (test performance metrics)

* docs: align pipeline appendix with Setup/Fleet naming

* chore: update test run timings

* v0.8.85: address PR #91 review findings - manifest, docs, mojibake, prune tests

- Get-AzLocalPipelineManifest: collapse legacy authentication-test +
  inventory-clusters rows into the merged setup-validate-and-inventory entry
- appendix-pipelines.md / README.md: replace removed filenames + old Step
  naming with Setup:/Fleet: numbering; fix section 13 file-layout block and
  section 14 reference; repair broken cross-doc anchors (README 8.1.1 ->
  #fleet-01, sideload.md -> #fleet-03); update present-tense Step.7 reference
- appendix-pipelines.md: reconcile Setup: 01 trigger docs to the shipped
  weekly Sunday 08:00 UTC cron
- fleet-update-status.yml: fix mojibake in YAML comment
- apply-updates-schedule.example.yml: replace Step.5/Step.7 with stable
  apply-updates.yml / Fleet: 04 references
- Tests: add 10 -PruneDeprecated regression tests (6 Copy- + 4 Update-)
  covering both-removed, single-removed, ID-mismatch-preserved, omitted-flag
  and -WhatIf paths

* docs: clarify sideload-catalog.example.yml header comment (v0.8.7 on-prem solution/SBE update sideloading)

* docs: fix grammar in sideload-catalog.example.yml header (introduce -> introduced)

* v0.8.86: rename onboarding pipelines Setup -> Config + clarify GitHub Environments are optional

- Rename the three onboarding workflow display names from `Setup: 0N` to
  `Config: 0N` (GitHub Actions `name:` and Azure DevOps `displayName:`/`name:`)
  so the Actions sidebar / ADO Pipelines list sorts the onboarding workflows
  ahead of the `Fleet: 0N` operational workflows (C sorts before F; the old
  `Setup:` prefix sorted after `Fleet:`). Display-name-only change - filenames,
  AZLOCAL-PIPELINE-ID values, aliases and prune logic are unchanged.
- Update bundled pipeline README.md + docs/appendix-pipelines.md (headings,
  cross-references, anchors, naming rationale) to the Config: NN naming.
- README.md (Automation-Pipeline-Examples): clarify that GitHub Environments
  are OPTIONAL. The branch-scoped federated credential is all OIDC needs, so a
  blank `environment` input is the supported minimal setup. Environments are a
  governance wrapper (approval gates, deployment-branch rules, wait timers,
  per-ring identities); environment-scoped federated credentials are only
  needed when a run actually names an environment. Mark the environment table,
  the inline + PowerShell env-scoped credential blocks, the subject-claim table
  row, and the section-5 secrets script accordingly.
- Version bump to 0.8.86: psd1 ModuleVersion + ReleaseNotes, psm1
  $script:ModuleVersion, CHANGELOG.md, both README files, docs/release-history,
  Tests version assertion, and all GENERATED_AGAINST_MODULE_VERSION pins across
  the bundled GitHub Actions and Azure DevOps templates.

Full Pester suite: 1266 passed, 0 failed, 1 skipped.

* ci: disable hosted Pester workflow (comment out pull_request + push triggers; keep workflow_dispatch). Suite is run locally before every push.

* v0.8.87: rename 'Orphan ARBs' section to 'Non-Azure Local and/or Orphan ARB appliances'

New-AzLocalFleetConnectivityStatusSummary (Fleet: 02) markdown output: rename the
Orphan ARBs section, add intro line, and expand the caveat to note that an Arc
resource bridge with no matching in-scope Azure Local cluster is NOT necessarily
orphaned - Arc resource bridge is also used by VMware vSphere and SCVMM. Adds
investigate-before-acting guidance. KPI note, causes list, and cluster-table
cross-reference updated to match. Output text only; no API or behavioural change.

Lock-step version bump 0.8.86 -> 0.8.87: psd1 (ModuleVersion + ReleaseNotes),
psm1 ($script:ModuleVersion), CHANGELOG, both README sections + appendix,
Tests assertion, docs/release-history.md, and all 20 GENERATED_AGAINST_MODULE_VERSION
pins. Full Pester suite green (1266 passed, 0 failed, 1 skipped, 38 not-run).

* v0.8.87: collapse Cluster Connectivity (with ARB Status) table by default

New-AzLocalFleetConnectivityStatusSummary now wraps the per-cluster Cluster
Connectivity (with ARB Status) table in a collapsed <details> block with an
'Expand to view clusters' summary, so the Fleet: 02 step summary stays compact.
Added a Pester assertion for the details/summary wrapper. Output text only; no
API or behavioural change. Release notes (psd1/CHANGELOG/README/release-history)
updated within the in-flight v0.8.87. Full Pester suite green (1267 passed,
0 failed, 1 skipped).

* v0.8.87: split Cluster Connectivity table into with/without connectivity issues

New-AzLocalFleetConnectivityStatusSummary now renders two per-cluster tables
instead of one:

- '### Cluster with Connectivity Issues' - clusters that are NOT (Connectivity =
  Connected AND ARB Status = Running). Shown first and expanded.
- '### Cluster without Connectivity Issues' - clusters that ARE Connected with a
  Running ARB. Collapsed behind an 'Expand to view clusters' details block.

Both tables share the same heading columns. Row rendering is factored into a
plain scriptblock (no .GetNewClosure()) reused by both tables. Added/updated
Pester assertions for both headings, the partitioning, and the collapsed block;
fixed the CSV-input context assertion that referenced the old single heading.

Release notes (psd1/CHANGELOG/README/release-history) updated within the
in-flight v0.8.87 (ReleaseNotes 9872 chars, under the 10000 limit). Full Pester
suite green (1270 passed, 0 failed, 1 skipped). Output text only; no API change.

* v0.8.87: rename bundled pipeline display names to Config:/Monitor:/Update: scheme

Renames all bundled pipeline display names (name: on GitHub Actions,
displayName:/name: on Azure DevOps) into a three-group single-digit scheme:
Config: 1-3 (onboarding/config), Monitor: 1-3 (day-2 fleet monitoring),
Update: 1-4 (update lifecycle), replacing the former Setup: 0N / Fleet: 0N
prefixes. Monitor: 2 is Fleet Health Status and Monitor: 3 is Fleet Update
Status so the numbering matches alphabetical order.

Display name only - filenames, AZLOCAL-PIPELINE-ID values, aliases, and
-PruneDeprecated logic are unchanged. Updates the bundled README,
appendix-pipelines.md (grouped/ordered conventions, alphabetical file layout),
ITSM docs, release docs, the manifest ReleaseNotes, CHANGELOG, the schedule
auditor's emitted markdown (Update: 4), and the matching Pester assertions.

Full suite green: 1282 passed, 0 failed, 1 skipped.

Author: NeilBird

AzLocal.UpdateManagement/Automation-Pipeline-Examples/.itsm/azurelocal-itsm.yml

@@ -48,3 +48,21 @@ triggers:
     raiseTicket: false
   NotReady:
     raiseTicket: false
+
+  # ----- Update: 4 - Monitor In-Flight Updates statuses (v0.8.87) -----
+  # Emitted by Export-AzLocalUpdateRunMonitorReport in update-monitor.xml.
+  # Wire monitor-updates.yml with raise_itsm_ticket=true to open tickets for
+  # these. Dedupe key = SHA256(ClusterResourceId|UpdateName|TriggerCategory),
+  # so a stuck/attempt-gap cluster opens at most ONE incident until it clears.
+  AttemptWithoutRun:
+    raiseTicket: true
+    severity: 3
+    category: "Update attempt with no observable updateRun"   # UpdateLastAttempt tag set, but no updateRun materialised (commonly a URP package pre-install health-check failure)
+  StepError:
+    raiseTicket: true
+    severity: 2
+    category: "Update step stuck in error"                    # progress.status == Error while state is still InProgress
+  LongRunningOverall:
+    raiseTicket: false   # informational backstop; opt-in if you want a ticket per run exceeding the overall-elapsed threshold
+  LongRunningStep:
+    raiseTicket: false   # informational; opt-in if you want a ticket per run whose current step exceeds the per-step threshold

AzLocal.UpdateManagement/Automation-Pipeline-Examples/README.md

@@ -27,7 +27,7 @@
 # A cron firing that lands on a day with NO matching schedule rows is
 # logged and exits 0 - no errors, no failures.
 #
-# This file is REQUIRED for the "Fleet: 04 - Apply Updates"
+# This file is REQUIRED for the "Update: 3 - Apply Updates"
 # (apply-updates.yml) pipeline when triggered by a schedule (not
 # workflow_dispatch). If the file is missing, apply-updates.yml throws
 # with the exact remediation command.

AzLocal.UpdateManagement/Automation-Pipeline-Examples/apply-updates-schedule.example.yml

@@ -1,5 +1,5 @@
 # AZLOCAL-PIPELINE-ID: apply-updates-schedule-audit
-# Config: 03 - Apply-Updates Schedule Coverage Audit Pipeline
+# Config: 3 - 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.86'
+  GENERATED_AGAINST_MODULE_VERSION: '0.8.87'
   REQUIRED_MODULE_VERSION: '${{ parameters.moduleVersion }}'
   reportsPath: '$(Build.ArtifactStagingDirectory)/reports'
   # v0.8.7 sideload advisor defaults. Override at the pipeline / variable-group
@@ -98,7 +98,7 @@ variables:
 
 stages:
 - stage: ScheduleCoverage
-  displayName: 'Config: 03 - Audit Apply-Updates Schedule Coverage'
+  displayName: 'Config: 3 - Audit Apply-Updates Schedule Coverage'
   jobs:
   - job: Audit
     displayName: 'Run Schedule Coverage Advisor'

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

@@ -1,5 +1,5 @@
 # AZLOCAL-PIPELINE-ID: apply-updates
-# Fleet: 04 - Apply Updates to Azure Local Clusters
+# Update: 3 - Apply Updates to Azure Local Clusters
 # This pipeline applies updates to clusters filtered by UpdateRing tag value
 
 # Author guidance lives OUTSIDE the customise markers so module refreshes
@@ -129,7 +129,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.86'
+    value: '0.8.87'
   # 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).
@@ -252,7 +252,7 @@ stages:
 
   # Stage 2: Apply Updates (with approval gate for production)
   - stage: ApplyUpdates
-    displayName: 'Fleet: 04 - Apply Updates'
+    displayName: 'Update: 3 - Apply Updates'
     dependsOn: CheckReadiness
     condition: and(succeeded(), gt(dependencies.CheckReadiness.outputs['ReadinessCheck.readiness.ReadyCount'], 0))
 

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

@@ -1,5 +1,5 @@
 # AZLOCAL-PIPELINE-ID: assess-update-readiness
-# Fleet: 01 - Assess Update Readiness (Pre-flight go/no-go gate)
+# Update: 1 - 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.86'
+  GENERATED_AGAINST_MODULE_VERSION: '0.8.87'
   # 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).
@@ -82,7 +82,7 @@ pool:
 
 stages:
   - stage: Assess
-    displayName: 'Fleet: 01 - Assess Update Readiness'
+    displayName: 'Update: 1 - Assess Update Readiness'
     jobs:
       - job: AssessReadiness
         displayName: 'Readiness + blocking health gate'

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

@@ -1,5 +1,5 @@
 # AZLOCAL-PIPELINE-ID: fleet-connectivity-status
-# Fleet: 02 - Fleet Connectivity Status Monitoring Pipeline
+# Monitor: 1 - 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: 'Fleet: 02 - Fleet Connectivity Status'
+name: 'Monitor: 1 - 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.86'
+  GENERATED_AGAINST_MODULE_VERSION: '0.8.87'
   # 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-health-status
-# Fleet: 07 - Fleet Health Status Monitoring Pipeline
+# Monitor: 2 - Fleet Health Status Monitoring Pipeline
 # This pipeline surfaces 24-hour system health-check failures across every Azure Local
 # cluster the service connection can read - including clusters that are already
 # "up to date" with no available updates. The 24-hour health checks continue to run
@@ -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.86'
+  GENERATED_AGAINST_MODULE_VERSION: '0.8.87'
   # 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

@@ -1,5 +1,5 @@
 # AZLOCAL-PIPELINE-ID: fleet-update-status
-# Fleet: 06 - Fleet Update Status Monitoring Pipeline
+# Monitor: 3 - 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.86'
+  GENERATED_AGAINST_MODULE_VERSION: '0.8.87'
   # 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: manage-updatering-tags
-# Config: 02 - Manage UpdateRing Tags
+# Config: 2 - 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.86'
+    value: '0.8.87'
   # 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).
@@ -58,7 +58,7 @@ pool:
 
 stages:
   - stage: ManageTags
-    displayName: 'Config: 02 - Manage UpdateRing Tags'
+    displayName: 'Config: 2 - Manage UpdateRing Tags'
     jobs:
       - job: ApplyTags
         displayName: 'Apply UpdateRing Tags'