You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Everything is OK—the changes have been pushed to branch workshop-content-sync-2026-09-21-4a39f290215ec134. Please review the changes, including any protected files, before creating the pull request.
Aligns Track 2/3 workshop content with the current Azure Deployment Stack-based deploy/destroy implementation, and adds three previously-undocumented skills to the glossary and relevant lab failure-mode tables.
What changed, and why
1. Fix drift: destroy lifecycle described the wrong teardown model
workshops/track-3-platform-engineering/lab-06-destroy-lifecycle.md — Steps 4–5 and the "Clean Up Remaining Resources" section described the old resource-group-deletion model (az group delete, "reads the resource group name from state.json", "deletes subscription-scoped resources first"). The actual behavior (confirmed against .github/skills/azure-stack-destroy/SKILL.md and the onboarding-scaffolded git-ape-destroy.yml template, and already correctly reflected in the Track 3 deck) is: read stackId from state.json, az stack sub show to inventory, then az stack sub delete --action-on-unmanage deleteAll --bypass-stack-out-of-sync-error true, followed by a soft-delete purge sweep. Rewrote the affected steps and cleanup snippet to match, and pointed learners at the azure-stack-destroy skill for local/VS Code teardown. Also removed a duplicate trailing "Step 6/7/8" block that restated (correctly) the same facts the earlier steps had gotten wrong — keeping one accurate description instead of two.
workshops/track-2-deploy-like-a-pro/lab-05-drift-detection.md — the "Clean up" pointer at the end used the same stale az group delete command; replaced with the azure-stack-destroy script invocation.
Persona/track: DevOps/SRE/platform engineers (Track 3, primary) and engineers doing hands-on cleanup (Track 2). Both personas need the teardown command they actually run to work.
2. Document previously-uncovered skills
workshops/track-3-platform-engineering/lab-01-cicd-pipeline.md — added a note that local/VS Code deploys use the azure-stack-deploy skill (same flags and state.json schema as the CI job), so the CI→local mapping is explicit.
workshops/track-2-deploy-like-a-pro/lab-02-web-app-sql.md — added azure-resource-availability to the SKU/quota common-failure table (SkuNotAvailable → run /azure-resource-availability to check restrictions and get alternatives).
workshops/shared/glossary.md — added glossary entries for azure-resource-availability, azure-stack-deploy, and azure-stack-destroy (all had 0 references in workshop content per the coverage inventory).
Persona/track: Engineer/developer (Track 2) for azure-resource-availability (a deployment-failure diagnostic they'd hit hands-on); DevOps/SRE (Track 3) for the stack deploy/destroy skills (CI/local parity is a platform-engineering concern).
Deferred (not changed this run)
azure-rest-api-reference skill — internal correctness aid used by azure-template-generator, no distinct learner-facing action to attach it to without inventing a scenario.
azure-requirements-gatherer agent — user-invocable: false, already implicitly exercised by every @git-ape deploy ... step across existing labs.
No-Azure fallback: not applicable — all touched labs are in Azure-required tracks (2 and 3); no fallback paths existed or were removed.
Binaries untouched: no .pdf/.pptx/.html files touched.
Deck lint rules: no *_deck.md files were modified in this PR.
Scope: only files under workshops/ were touched; no changes to .github/, source code, or this workflow.
Related
Coverage report: see the linked Workshop Coverage Status issue for this run's full assessment.
Note
GitHub Actions is not permitted to create or approve pull requests in this repository.
The changes have been pushed to branch workshop-content-sync-2026-09-21-4a39f290215ec134 and are ready to review.
To fix the permissions issue, go to Settings → Actions → General and enable Allow GitHub Actions to create and approve pull requests. See also: gh-aw FAQ
Show patch preview (38 of 177 lines)
From 7c56f2374f74be9b4acb95c341b15381443983ac Mon Sep 17 00:00:00 2001
X-GH-AW-Base-Commit: c58302b59dbe213321903542b0db2eb2c48c0062
From: "github-actions[bot]" <github-actions[bot]@users.noreply.github.com>
Date: Mon, 21 Sep 2026 21:00:32 +0000
Subject: [PATCH] docs(workshops): align destroy lifecycle content with Azure
Deployment Stacks
- Fix Track 3 Lab 6 (destroy lifecycle): replace stale az group delete /
resource-group-deletion description with the actual Deployment Stack
teardown (az stack sub delete --action-on-unmanage deleteAll), soft-delete
purge sweep, and the azure-stack-destroy skill for local/VS Code teardown.
Removes a duplicate trailing section that restated (correctly) what the
main steps had described incorrectly.
- Fix Track 2 Lab 5 cleanup snippet: same stack-based teardown instead of
az group delete.
- Track 3 Lab 1: note that local/VS Code deploys use the azure-stack-deploy
skill (same flags/state.json schema as the CI job).
- Track 2 Lab 2: add azure-resource-availability skill to the SKU/quota
failure-mode table.
- Glossary: add azure-resource-availability, azure-stack-deploy, and
azure-stack-destroy skill entries (previously undocumented).
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---
workshops/shared/glossary.md | 3 ++
.../lab-02-web-app-sql.md | 1 +
.../lab-05-drift-detection.md | 4 +-
.../lab-01-cicd-pipeline.md | 2 +
.../lab-06-destroy-lifecycle.md | 53 ++++++++-----------
5 files changed, 30 insertions(+), 33 deletions(-)
diff --git a/workshops/shared/glossary.md b/workshops/shared/glossary.md
index 48cf741..0eb714f 100644
--- a/workshops/shared/glossary.md+++ b/workshops/shared/glossary.md@@ -47,4 +47,7 @@
| `/azure-role-selector` | Recommends least-privilege RBAC roles for identities and resources. |
| `/azure-policy-advisor` | Assesses templates against compliance frameworks and recommen
... (truncated)
Tip
Your pull request is ready to create! 🎉 ✅
Everything is OK—the changes have been pushed to branch
workshop-content-sync-2026-09-21-4a39f290215ec134. Please review the changes, including any protected files, before creating the pull request.Create the pull request
The original pull request description is below.
Summary
Aligns Track 2/3 workshop content with the current Azure Deployment Stack-based deploy/destroy implementation, and adds three previously-undocumented skills to the glossary and relevant lab failure-mode tables.
What changed, and why
1. Fix drift: destroy lifecycle described the wrong teardown model
workshops/track-3-platform-engineering/lab-06-destroy-lifecycle.md— Steps 4–5 and the "Clean Up Remaining Resources" section described the old resource-group-deletion model (az group delete, "reads the resource group name fromstate.json", "deletes subscription-scoped resources first"). The actual behavior (confirmed against.github/skills/azure-stack-destroy/SKILL.mdand the onboarding-scaffoldedgit-ape-destroy.ymltemplate, and already correctly reflected in the Track 3 deck) is: readstackIdfromstate.json,az stack sub showto inventory, thenaz stack sub delete --action-on-unmanage deleteAll --bypass-stack-out-of-sync-error true, followed by a soft-delete purge sweep. Rewrote the affected steps and cleanup snippet to match, and pointed learners at theazure-stack-destroyskill for local/VS Code teardown. Also removed a duplicate trailing "Step 6/7/8" block that restated (correctly) the same facts the earlier steps had gotten wrong — keeping one accurate description instead of two.workshops/track-2-deploy-like-a-pro/lab-05-drift-detection.md— the "Clean up" pointer at the end used the same staleaz group deletecommand; replaced with theazure-stack-destroyscript invocation.Persona/track: DevOps/SRE/platform engineers (Track 3, primary) and engineers doing hands-on cleanup (Track 2). Both personas need the teardown command they actually run to work.
2. Document previously-uncovered skills
workshops/track-3-platform-engineering/lab-01-cicd-pipeline.md— added a note that local/VS Code deploys use theazure-stack-deployskill (same flags andstate.jsonschema as the CI job), so the CI→local mapping is explicit.workshops/track-2-deploy-like-a-pro/lab-02-web-app-sql.md— addedazure-resource-availabilityto the SKU/quota common-failure table (SkuNotAvailable→ run/azure-resource-availabilityto check restrictions and get alternatives).workshops/shared/glossary.md— added glossary entries forazure-resource-availability,azure-stack-deploy, andazure-stack-destroy(all had 0 references in workshop content per the coverage inventory).Persona/track: Engineer/developer (Track 2) for
azure-resource-availability(a deployment-failure diagnostic they'd hit hands-on); DevOps/SRE (Track 3) for the stack deploy/destroy skills (CI/local parity is a platform-engineering concern).Deferred (not changed this run)
azure-rest-api-referenceskill — internal correctness aid used byazure-template-generator, no distinct learner-facing action to attach it to without inventing a scenario.azure-requirements-gathereragent —user-invocable: false, already implicitly exercised by every@git-ape deploy ...step across existing labs.See the coverage-status issue for full reasoning.
Guardrails confirmed
.pdf/.pptx/.htmlfiles touched.*_deck.mdfiles were modified in this PR.workshops/were touched; no changes to.github/, source code, or this workflow.Related
Workshop Coverage Statusissue for this run's full assessment.Note
GitHub Actions is not permitted to create or approve pull requests in this repository.
To fix the permissions issue, go to Settings → Actions → General and enable Allow GitHub Actions to create and approve pull requests. See also: gh-aw FAQ
Show patch preview (38 of 177 lines)