v0.8.87: pipeline display-name rename (Config/Monitor/Update) + connectivity output + monitor ITSM#93
Merged
Merged
Conversation
… ADO setup pipeline
…AzLocalAuthValidationReport cmdlet; track test-run-timings.csv
…tionPreference, Step.3 path, Step.4 SummaryPath)
…rune 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
…prem solution/SBE update sideloading)
… 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.
…riggers; keep workflow_dispatch). Suite is run locally before every push.
…an 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).
…ault 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).
…ity 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.
…date: 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.
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.
v0.8.87
Brings the v0.8.87 changes to
main. Net diff vsmainis the v0.8.87 work(v0.8.85/0.8.86 already landed via squash-merge #92).
Pipeline display-name rename (headline)
Renames all bundled pipeline display names (
name:on GitHub Actions,displayName:/name:on Azure DevOps) into a three-group single-digit scheme:This replaces the former
Setup: 0N/Fleet: 0Nprefixes.Monitor: 2isFleet Health Status and
Monitor: 3is Fleet Update Status, numbered to matchalphabetical order. Display name only - filenames,
AZLOCAL-PIPELINE-IDvalues, aliases, and
-PruneDeprecatedlogic are unchanged.Docs updated to match: bundled
README.md,docs/appendix-pipelines.md(category-grouped conceptual lists, alphabetical file-layout tree), ITSM docs,
release docs, manifest
ReleaseNotes,CHANGELOG.md, the schedule auditor'semitted markdown (
Update: 4), and the matching Pester assertions.Fleet Connectivity Status output
appliances" with an investigate-before-acting caveat (Arc resource bridge
is also used by VMware vSphere / SCVMM).
and a collapsed without-issues table.
In-flight monitor ITSM auto-ticketing
Export-AzLocalUpdateRunMonitorReport(Update: 4) writes per-<testcase><properties>soNew-AzLocalIncidentcan dedupe + deep-link.monitor-updates.ymlgains an opt-in ITSM ticketing step.Export-AzLocalApplyUpdatesScheduleAudit(Config: 3) recommends anUpdate: 4monitor poll cadence (-MonitorFiresPerHour,-MonitorTrailingDays).Validation
Full Pester suite green locally: 1282 passed, 0 failed, 1 skipped. No new
exports (count unchanged at 60).
GENERATED_AGAINST_MODULE_VERSIONbumped to0.8.87.