v0.8.86: rename onboarding pipelines Setup -> Config + clarify GitHub Environments are optional#92
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.
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
Ships AzLocal.UpdateManagement v0.8.86 plus a few post-#91 documentation cleanups.
v0.8.86 - rename onboarding pipelines
Setup:->Config:+ clarify GitHub Environments are optionalPipeline display-name rename (UX/sort order)
Setup: 0NtoConfig: 0Nacross both GitHub Actions (name:) and Azure DevOps (displayName:/name:) templates.Fleet: 0Noperational workflows (both surfaces sort alphabetically;Csorts beforeF, whereas the oldSetup:prefix sorted afterFleet:).AZLOCAL-PIPELINE-IDvalues, aliases, and-PruneDeprecatedlogic are all unchanged. No public API or behavioural change. Export count unchanged (still 60).Docs: GitHub Environments are optional
README.md(step 3, "federate the workflow") that GitHub Environments are optional. The branch-scoped federated credential is all OIDC requires, so leaving theenvironmentinput blank is the supported minimal setup.Version bump (lock-step)
psd1ModuleVersion + ReleaseNotes,psm1$script:ModuleVersion,CHANGELOG.md, bothREADME.mdfiles,docs/release-history.md, the Tests version assertion, and allGENERATED_AGAINST_MODULE_VERSIONpins across the bundled GitHub Actions and Azure DevOps templates ->0.8.86.Post-#91 doc cleanups (also included)
sideload-catalog.example.ymlheader comment clarified + grammar fix.Testing
Full Pester suite: 1266 passed, 0 failed, 1 skipped (38 not-run = az-CLI live integration tests).