[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-azure-sdaf-ado-project-bootstrap":3,"mdc--rc4j2u-key":35,"related-org-azure-sdaf-ado-project-bootstrap":864,"related-repo-azure-sdaf-ado-project-bootstrap":1039},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":12,"stars":24,"repoUrl":25,"updatedAt":26,"license":27,"forks":28,"topics":29,"repo":30,"sourceUrl":33,"mdContent":34},"sdaf-ado-project-bootstrap","bootstrap SDAF projects on Azure DevOps","Set up SDAF on Azure DevOps end-to-end: create the Azure DevOps project,\nconfiguration repository, pipelines, cleanup task, agent pool, control-plane\nmanaged identity, service connections, variable groups, optional Web App,\nand onboard each SDAF workload zone. Drives the documented\nNew-SDAFUserAssignedIdentity + New-SDAFADOProject + New-SDAFADOWorkloadZone\npath from docs\u002F02-00-bootstrap.md, docs\u002F02-10-configure-devops-project.md,\nand docs\u002F02-20-configure-workload-zone-artifacts.md. Use when an operator\nsays: \"set up SDAF on Azure DevOps\", \"bootstrap the ADO project\", \"onboard\na workload zone\", \"create a new SDAF DevOps project\", \"add SDAF-\u003Cenv>\nvariable group and service connection\". NOT for what an individual pipeline\ndoes or when to run it (see sdaf-ado-pipeline-catalogue), and not for the\nGitHub Actions surface.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},"azure","Azure (Microsoft)","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fazure.png","Azure",[13,15,18,21],{"name":11,"slug":8,"type":14},"tag",{"name":16,"slug":17,"type":14},"Automation","automation",{"name":19,"slug":20,"type":14},"Azure DevOps","azure-devops",{"name":22,"slug":23,"type":14},"SAP","sap",11,"https:\u002F\u002Fgithub.com\u002FAzure\u002Fsap-automation-bootstrap","2026-09-02T07:46:51.024319","MIT",20,[],{"repoUrl":25,"stars":24,"forks":28,"topics":31,"description":32},[],"Bootstrap repo for SDAF","https:\u002F\u002Fgithub.com\u002FAzure\u002Fsap-automation-bootstrap\u002Ftree\u002FHEAD\u002Fskills\u002Fsdaf-ado-project-bootstrap","---\nname: sdaf-ado-project-bootstrap\ndescription: |\n  Set up SDAF on Azure DevOps end-to-end: create the Azure DevOps project,\n  configuration repository, pipelines, cleanup task, agent pool, control-plane\n  managed identity, service connections, variable groups, optional Web App,\n  and onboard each SDAF workload zone. Drives the documented\n  New-SDAFUserAssignedIdentity + New-SDAFADOProject + New-SDAFADOWorkloadZone\n  path from docs\u002F02-00-bootstrap.md, docs\u002F02-10-configure-devops-project.md,\n  and docs\u002F02-20-configure-workload-zone-artifacts.md. Use when an operator\n  says: \"set up SDAF on Azure DevOps\", \"bootstrap the ADO project\", \"onboard\n  a workload zone\", \"create a new SDAF DevOps project\", \"add SDAF-\u003Cenv>\n  variable group and service connection\". NOT for what an individual pipeline\n  does or when to run it (see sdaf-ado-pipeline-catalogue), and not for the\n  GitHub Actions surface.\nlicense: MIT\n---\n\n# SDAF — Azure DevOps project bootstrap and workload-zone onboarding\n\nDrives the two documented PowerShell utilities that create the SDAF Azure\nDevOps footprint: `New-SDAFADOProject` (project + control-plane artifacts) and\n`New-SDAFADOWorkloadZone` (variable group + service connection for each extra\nworkload environment). Same script family, same doc pages, one operator sitting. Documented in\n[`docs\u002F02-00-bootstrap.md`](..\u002F..\u002Fdocs\u002F02-00-bootstrap.md),\n[`docs\u002F02-10-configure-devops-project.md`](..\u002F..\u002Fdocs\u002F02-10-configure-devops-project.md),\nand [`docs\u002F02-20-configure-workload-zone-artifacts.md`](..\u002F..\u002Fdocs\u002F02-20-configure-workload-zone-artifacts.md).\n\n## When to invoke\n\nTrigger utterances: \"set up SDAF on Azure DevOps\", \"bootstrap the Azure\nDevOps project\", \"create the SDAF-MGMT-SECE project\", \"add \u002F onboard the\nTEST-SECE-SAP01 workload zone\", \"create the SDAF-\u003Cenv> variable group and\nworkload service connection\".\n\nDo **not** invoke for: \"what does pipeline `01` do?\" or \"which variable group\ndoes `05` read?\" (→ `sdaf-ado-pipeline-catalogue`); anything on the GitHub\nActions surface; or actually deploying the control plane, workload zone, or\nSAP system (bootstrap creates artefacts; deployment is a separate hub-plugin\nskill).\n\n## Recipe\n\nBoth journeys run from Windows PowerShell with the latest Azure CLI, download\n`SDAFUtilities.psm1` from the reviewed `sap-automation` ref, sign in, run the\nutility, capture returned values.\n\n### A. First-time project bootstrap\n\n1. Confirm inputs listed at the top of\n   `docs\u002F02-10-configure-devops-project.md` (see also\n   [`docs\u002F01-00-prerequisites.md`](..\u002F..\u002Fdocs\u002F01-00-prerequisites.md)):\n   Azure DevOps organization URL, tenant ID, control-plane subscription ID,\n   control-plane and region codes, agent-pool name, SAP support credentials,\n   reviewed `sap-automation` branch, `SDAF-MSIs` resource group.\n2. Copy the script in `docs\u002F02-10-configure-devops-project.md § Configure the script` into a local `.ps1`. Replace every placeholder. Drop `-EnableWebApp` when the configuration Web App is not in scope.\n3. `az upgrade`, sign in to the intended Azure tenant, then run the `.ps1`;\n   complete each browser prompt the utilities open.\n4. Wait for `New-SDAFADOProject` to finish. Record the project URL, the\n   managed-identity ID from `New-SDAFUserAssignedIdentity`, and the\n   agent-pool name.\n\n### B. Onboarding an additional workload zone\n\nPrerequisite: the project and control-plane MSI from A already exist.\n\n1. Copy the script in `docs\u002F02-20-configure-workload-zone-artifacts.md § Configure the script`. Reuse `$ControlPlaneCode`, `$ControlPlaneRegionCode`, `$ManagedIdentityName`, `$MSIResourceGroupName` from A; set `$WorkloadCode`, `$WorkloadRegionCode`, and `$WorkloadSubscriptionId`.\n2. Sign in to the tenant that holds the control-plane MSI. Run the `.ps1`\n   and confirm `Get-SDAFUserAssignedIdentity` returns the control-plane\n   identity before `New-SDAFADOWorkloadZone` runs.\n\n### C. Validate concretely after either journey\n\nWalk the \"Validate\" section of the matching configure page\n([A: `docs\u002F02-10-configure-devops-project.md`](..\u002F..\u002Fdocs\u002F02-10-configure-devops-project.md);\n[B: `docs\u002F02-20-configure-workload-zone-artifacts.md`](..\u002F..\u002Fdocs\u002F02-20-configure-workload-zone-artifacts.md)):\n\n1. Project exists with the expected name; configuration repository contains\n   `pipelines` and `WORKSPACES`\n   (`docs\u002F02-00-bootstrap.md § Create the project and configuration repository`).\n2. Deployment pipelines were created — canonical inventory and variable-group\n   mapping is `sdaf-ado-pipeline-catalogue § Variable-group dependencies`;\n   do not restate it here.\n3. Sensitive values (`S-Password`, PAT, Azure credentials) are marked secret.\n4. Every service connection targets the correct subscription and tenant.\n5. Agent pool exists and required pipelines are authorized on it.\n6. Build Service has the repository permissions the pipelines need\n   (`docs\u002F02-00-bootstrap.md § Configure service connections and permissions`).\n7. No SAP password, PAT, or Azure credential appears in source control or\n   pipeline logs.\n\n\n## Hard rules\n\n1. **Documented utilities only.** Drive `New-SDAFUserAssignedIdentity`,\n   `New-SDAFADOProject`, `Get-SDAFUserAssignedIdentity`, and\n   `New-SDAFADOWorkloadZone` as documented. `setup_ado.sh` and\n   `configure_deployer.sh` are named in\n   `docs\u002F02-00-bootstrap.md § Configure the agent` as Learn-article steps —\n   drive them only via that path; their internals are not documented here.\n   Other ADO-setup scripts (`create_devops_artifacts.sh`,\n   `New-SDAFDevopsProject.ps1`, `New-SDAFDevopsWorkloadZone.ps1`,\n   `setup_devops.ps1`, `Upgrade-*`) are not documented here at all — do not\n   reconstruct their behaviour.\n2. **Never invent parameters, roles, or variable-group values.** The\n   per-variable catalogue for `SDAF-\u003Cenvironment>` is not exhaustively\n   documented; state the gap, do not guess.\n3. **Credential hygiene.** Read SAP support credentials with\n   `Read-Host -AsSecureString`, do not echo, and remove `Env:SUserName` \u002F\n   `Env:SPassword` in a `finally` block exactly as\n   `docs\u002F02-10-configure-devops-project.md § Configure the script` shows.\n4. **Do not rerun a partial script blind.** Inventory what was created,\n   correct the first failed dependency, then rerun with the same project and\n   control-plane names (`docs\u002F02-00-bootstrap.md § If it fails`).\n5. **Reuse the workload-zone code.** Same `$WorkloadZoneCode` updates in\n   place; a new code creates duplicate artefacts.\n6. **`WORKSPACES\u002FLANDSCAPE\u002F\u003Czone>\u002F\u003Czone>.tfvars` is not created here** — it\n   is a prerequisite of the `02` deployment pipeline.\n\n## What this skill does NOT do\n\nChoose between automated and manual paths (`docs\u002F02-00-bootstrap.md § Manual\nconfiguration path` is a fallback the operator invokes directly); deploy the\ncontrol plane, workload zone, or any SAP system; explain individual pipeline\nparameters or run order (see `sdaf-ado-pipeline-catalogue`); cover the\nGitHub Actions bootstrap (`sap-automation-gh-bootstrap`); register the\ndeployer VM as the self-hosted agent (that happens during control-plane\ndeployment — `docs\u002F02-00-bootstrap.md § Configure the agent` points 3–4); or\nauthor \u002F debug `SDAFUtilities.psm1` itself.\n\n## See also\n\n`sdaf-ado-pipeline-catalogue` — what each of the 13 pipeline wrappers does,\nthe variable groups they read, and the `20`\u002F`21`\u002F`22` level-up path.\n[`docs\u002Ftroubleshooting.md`](..\u002F..\u002Fdocs\u002Ftroubleshooting.md) — first-triage\nfor PAT\u002Fauthorization, variable groups, service connections, and agents.",{"data":36,"body":37},{"name":4,"description":6,"license":27},{"type":38,"children":39},"root",[40,49,109,116,127,164,170,191,198,309,315,320,414,420,449,534,540,765,771,813,819],{"type":41,"tag":42,"props":43,"children":45},"element","h1",{"id":44},"sdaf-azure-devops-project-bootstrap-and-workload-zone-onboarding",[46],{"type":47,"value":48},"text","SDAF — Azure DevOps project bootstrap and workload-zone onboarding",{"type":41,"tag":50,"props":51,"children":52},"p",{},[53,55,62,64,70,72,83,85,95,97,107],{"type":47,"value":54},"Drives the two documented PowerShell utilities that create the SDAF Azure\nDevOps footprint: ",{"type":41,"tag":56,"props":57,"children":59},"code",{"className":58},[],[60],{"type":47,"value":61},"New-SDAFADOProject",{"type":47,"value":63}," (project + control-plane artifacts) and\n",{"type":41,"tag":56,"props":65,"children":67},{"className":66},[],[68],{"type":47,"value":69},"New-SDAFADOWorkloadZone",{"type":47,"value":71}," (variable group + service connection for each extra\nworkload environment). Same script family, same doc pages, one operator sitting. Documented in\n",{"type":41,"tag":73,"props":74,"children":76},"a",{"href":75},"..\u002F..\u002Fdocs\u002F02-00-bootstrap.md",[77],{"type":41,"tag":56,"props":78,"children":80},{"className":79},[],[81],{"type":47,"value":82},"docs\u002F02-00-bootstrap.md",{"type":47,"value":84},",\n",{"type":41,"tag":73,"props":86,"children":88},{"href":87},"..\u002F..\u002Fdocs\u002F02-10-configure-devops-project.md",[89],{"type":41,"tag":56,"props":90,"children":92},{"className":91},[],[93],{"type":47,"value":94},"docs\u002F02-10-configure-devops-project.md",{"type":47,"value":96},",\nand ",{"type":41,"tag":73,"props":98,"children":100},{"href":99},"..\u002F..\u002Fdocs\u002F02-20-configure-workload-zone-artifacts.md",[101],{"type":41,"tag":56,"props":102,"children":104},{"className":103},[],[105],{"type":47,"value":106},"docs\u002F02-20-configure-workload-zone-artifacts.md",{"type":47,"value":108},".",{"type":41,"tag":110,"props":111,"children":113},"h2",{"id":112},"when-to-invoke",[114],{"type":47,"value":115},"When to invoke",{"type":41,"tag":50,"props":117,"children":118},{},[119,121],{"type":47,"value":120},"Trigger utterances: \"set up SDAF on Azure DevOps\", \"bootstrap the Azure\nDevOps project\", \"create the SDAF-MGMT-SECE project\", \"add \u002F onboard the\nTEST-SECE-SAP01 workload zone\", \"create the SDAF-",{"type":41,"tag":122,"props":123,"children":124},"env",{},[125],{"type":47,"value":126}," variable group and\nworkload service connection\".",{"type":41,"tag":50,"props":128,"children":129},{},[130,132,138,140,146,148,154,156,162],{"type":47,"value":131},"Do ",{"type":41,"tag":133,"props":134,"children":135},"strong",{},[136],{"type":47,"value":137},"not",{"type":47,"value":139}," invoke for: \"what does pipeline ",{"type":41,"tag":56,"props":141,"children":143},{"className":142},[],[144],{"type":47,"value":145},"01",{"type":47,"value":147}," do?\" or \"which variable group\ndoes ",{"type":41,"tag":56,"props":149,"children":151},{"className":150},[],[152],{"type":47,"value":153},"05",{"type":47,"value":155}," read?\" (→ ",{"type":41,"tag":56,"props":157,"children":159},{"className":158},[],[160],{"type":47,"value":161},"sdaf-ado-pipeline-catalogue",{"type":47,"value":163},"); anything on the GitHub\nActions surface; or actually deploying the control plane, workload zone, or\nSAP system (bootstrap creates artefacts; deployment is a separate hub-plugin\nskill).",{"type":41,"tag":110,"props":165,"children":167},{"id":166},"recipe",[168],{"type":47,"value":169},"Recipe",{"type":41,"tag":50,"props":171,"children":172},{},[173,175,181,183,189],{"type":47,"value":174},"Both journeys run from Windows PowerShell with the latest Azure CLI, download\n",{"type":41,"tag":56,"props":176,"children":178},{"className":177},[],[179],{"type":47,"value":180},"SDAFUtilities.psm1",{"type":47,"value":182}," from the reviewed ",{"type":41,"tag":56,"props":184,"children":186},{"className":185},[],[187],{"type":47,"value":188},"sap-automation",{"type":47,"value":190}," ref, sign in, run the\nutility, capture returned values.",{"type":41,"tag":192,"props":193,"children":195},"h3",{"id":194},"a-first-time-project-bootstrap",[196],{"type":47,"value":197},"A. First-time project bootstrap",{"type":41,"tag":199,"props":200,"children":201},"ol",{},[202,242,271,289],{"type":41,"tag":203,"props":204,"children":205},"li",{},[206,208,213,215,225,227,232,234,240],{"type":47,"value":207},"Confirm inputs listed at the top of\n",{"type":41,"tag":56,"props":209,"children":211},{"className":210},[],[212],{"type":47,"value":94},{"type":47,"value":214}," (see also\n",{"type":41,"tag":73,"props":216,"children":218},{"href":217},"..\u002F..\u002Fdocs\u002F01-00-prerequisites.md",[219],{"type":41,"tag":56,"props":220,"children":222},{"className":221},[],[223],{"type":47,"value":224},"docs\u002F01-00-prerequisites.md",{"type":47,"value":226},"):\nAzure DevOps organization URL, tenant ID, control-plane subscription ID,\ncontrol-plane and region codes, agent-pool name, SAP support credentials,\nreviewed ",{"type":41,"tag":56,"props":228,"children":230},{"className":229},[],[231],{"type":47,"value":188},{"type":47,"value":233}," branch, ",{"type":41,"tag":56,"props":235,"children":237},{"className":236},[],[238],{"type":47,"value":239},"SDAF-MSIs",{"type":47,"value":241}," resource group.",{"type":41,"tag":203,"props":243,"children":244},{},[245,247,253,255,261,263,269],{"type":47,"value":246},"Copy the script in ",{"type":41,"tag":56,"props":248,"children":250},{"className":249},[],[251],{"type":47,"value":252},"docs\u002F02-10-configure-devops-project.md § Configure the script",{"type":47,"value":254}," into a local ",{"type":41,"tag":56,"props":256,"children":258},{"className":257},[],[259],{"type":47,"value":260},".ps1",{"type":47,"value":262},". Replace every placeholder. Drop ",{"type":41,"tag":56,"props":264,"children":266},{"className":265},[],[267],{"type":47,"value":268},"-EnableWebApp",{"type":47,"value":270}," when the configuration Web App is not in scope.",{"type":41,"tag":203,"props":272,"children":273},{},[274,280,282,287],{"type":41,"tag":56,"props":275,"children":277},{"className":276},[],[278],{"type":47,"value":279},"az upgrade",{"type":47,"value":281},", sign in to the intended Azure tenant, then run the ",{"type":41,"tag":56,"props":283,"children":285},{"className":284},[],[286],{"type":47,"value":260},{"type":47,"value":288},";\ncomplete each browser prompt the utilities open.",{"type":41,"tag":203,"props":290,"children":291},{},[292,294,299,301,307],{"type":47,"value":293},"Wait for ",{"type":41,"tag":56,"props":295,"children":297},{"className":296},[],[298],{"type":47,"value":61},{"type":47,"value":300}," to finish. Record the project URL, the\nmanaged-identity ID from ",{"type":41,"tag":56,"props":302,"children":304},{"className":303},[],[305],{"type":47,"value":306},"New-SDAFUserAssignedIdentity",{"type":47,"value":308},", and the\nagent-pool name.",{"type":41,"tag":192,"props":310,"children":312},{"id":311},"b-onboarding-an-additional-workload-zone",[313],{"type":47,"value":314},"B. Onboarding an additional workload zone",{"type":41,"tag":50,"props":316,"children":317},{},[318],{"type":47,"value":319},"Prerequisite: the project and control-plane MSI from A already exist.",{"type":41,"tag":199,"props":321,"children":322},{},[323,387],{"type":41,"tag":203,"props":324,"children":325},{},[326,327,333,335,341,343,349,350,356,357,363,365,371,372,378,380,386],{"type":47,"value":246},{"type":41,"tag":56,"props":328,"children":330},{"className":329},[],[331],{"type":47,"value":332},"docs\u002F02-20-configure-workload-zone-artifacts.md § Configure the script",{"type":47,"value":334},". Reuse ",{"type":41,"tag":56,"props":336,"children":338},{"className":337},[],[339],{"type":47,"value":340},"$ControlPlaneCode",{"type":47,"value":342},", ",{"type":41,"tag":56,"props":344,"children":346},{"className":345},[],[347],{"type":47,"value":348},"$ControlPlaneRegionCode",{"type":47,"value":342},{"type":41,"tag":56,"props":351,"children":353},{"className":352},[],[354],{"type":47,"value":355},"$ManagedIdentityName",{"type":47,"value":342},{"type":41,"tag":56,"props":358,"children":360},{"className":359},[],[361],{"type":47,"value":362},"$MSIResourceGroupName",{"type":47,"value":364}," from A; set ",{"type":41,"tag":56,"props":366,"children":368},{"className":367},[],[369],{"type":47,"value":370},"$WorkloadCode",{"type":47,"value":342},{"type":41,"tag":56,"props":373,"children":375},{"className":374},[],[376],{"type":47,"value":377},"$WorkloadRegionCode",{"type":47,"value":379},", and ",{"type":41,"tag":56,"props":381,"children":383},{"className":382},[],[384],{"type":47,"value":385},"$WorkloadSubscriptionId",{"type":47,"value":108},{"type":41,"tag":203,"props":388,"children":389},{},[390,392,397,399,405,407,412],{"type":47,"value":391},"Sign in to the tenant that holds the control-plane MSI. Run the ",{"type":41,"tag":56,"props":393,"children":395},{"className":394},[],[396],{"type":47,"value":260},{"type":47,"value":398},"\nand confirm ",{"type":41,"tag":56,"props":400,"children":402},{"className":401},[],[403],{"type":47,"value":404},"Get-SDAFUserAssignedIdentity",{"type":47,"value":406}," returns the control-plane\nidentity before ",{"type":41,"tag":56,"props":408,"children":410},{"className":409},[],[411],{"type":47,"value":69},{"type":47,"value":413}," runs.",{"type":41,"tag":192,"props":415,"children":417},{"id":416},"c-validate-concretely-after-either-journey",[418],{"type":47,"value":419},"C. Validate concretely after either journey",{"type":41,"tag":50,"props":421,"children":422},{},[423,425,435,437,447],{"type":47,"value":424},"Walk the \"Validate\" section of the matching configure page\n(",{"type":41,"tag":73,"props":426,"children":427},{"href":87},[428,430],{"type":47,"value":429},"A: ",{"type":41,"tag":56,"props":431,"children":433},{"className":432},[],[434],{"type":47,"value":94},{"type":47,"value":436},";\n",{"type":41,"tag":73,"props":438,"children":439},{"href":99},[440,442],{"type":47,"value":441},"B: ",{"type":41,"tag":56,"props":443,"children":445},{"className":444},[],[446],{"type":47,"value":106},{"type":47,"value":448},"):",{"type":41,"tag":199,"props":450,"children":451},{},[452,481,494,507,512,517,529],{"type":41,"tag":203,"props":453,"children":454},{},[455,457,463,465,471,473,479],{"type":47,"value":456},"Project exists with the expected name; configuration repository contains\n",{"type":41,"tag":56,"props":458,"children":460},{"className":459},[],[461],{"type":47,"value":462},"pipelines",{"type":47,"value":464}," and ",{"type":41,"tag":56,"props":466,"children":468},{"className":467},[],[469],{"type":47,"value":470},"WORKSPACES",{"type":47,"value":472},"\n(",{"type":41,"tag":56,"props":474,"children":476},{"className":475},[],[477],{"type":47,"value":478},"docs\u002F02-00-bootstrap.md § Create the project and configuration repository",{"type":47,"value":480},").",{"type":41,"tag":203,"props":482,"children":483},{},[484,486,492],{"type":47,"value":485},"Deployment pipelines were created — canonical inventory and variable-group\nmapping is ",{"type":41,"tag":56,"props":487,"children":489},{"className":488},[],[490],{"type":47,"value":491},"sdaf-ado-pipeline-catalogue § Variable-group dependencies",{"type":47,"value":493},";\ndo not restate it here.",{"type":41,"tag":203,"props":495,"children":496},{},[497,499,505],{"type":47,"value":498},"Sensitive values (",{"type":41,"tag":56,"props":500,"children":502},{"className":501},[],[503],{"type":47,"value":504},"S-Password",{"type":47,"value":506},", PAT, Azure credentials) are marked secret.",{"type":41,"tag":203,"props":508,"children":509},{},[510],{"type":47,"value":511},"Every service connection targets the correct subscription and tenant.",{"type":41,"tag":203,"props":513,"children":514},{},[515],{"type":47,"value":516},"Agent pool exists and required pipelines are authorized on it.",{"type":41,"tag":203,"props":518,"children":519},{},[520,522,528],{"type":47,"value":521},"Build Service has the repository permissions the pipelines need\n(",{"type":41,"tag":56,"props":523,"children":525},{"className":524},[],[526],{"type":47,"value":527},"docs\u002F02-00-bootstrap.md § Configure service connections and permissions",{"type":47,"value":480},{"type":41,"tag":203,"props":530,"children":531},{},[532],{"type":47,"value":533},"No SAP password, PAT, or Azure credential appears in source control or\npipeline logs.",{"type":41,"tag":110,"props":535,"children":537},{"id":536},"hard-rules",[538],{"type":47,"value":539},"Hard rules",{"type":41,"tag":199,"props":541,"children":542},{},[543,639,657,706,723,741],{"type":41,"tag":203,"props":544,"children":545},{},[546,551,553,558,559,564,565,570,572,577,579,585,587,593,595,601,603,609,610,616,617,623,624,630,631,637],{"type":41,"tag":133,"props":547,"children":548},{},[549],{"type":47,"value":550},"Documented utilities only.",{"type":47,"value":552}," Drive ",{"type":41,"tag":56,"props":554,"children":556},{"className":555},[],[557],{"type":47,"value":306},{"type":47,"value":84},{"type":41,"tag":56,"props":560,"children":562},{"className":561},[],[563],{"type":47,"value":61},{"type":47,"value":342},{"type":41,"tag":56,"props":566,"children":568},{"className":567},[],[569],{"type":47,"value":404},{"type":47,"value":571},", and\n",{"type":41,"tag":56,"props":573,"children":575},{"className":574},[],[576],{"type":47,"value":69},{"type":47,"value":578}," as documented. ",{"type":41,"tag":56,"props":580,"children":582},{"className":581},[],[583],{"type":47,"value":584},"setup_ado.sh",{"type":47,"value":586}," and\n",{"type":41,"tag":56,"props":588,"children":590},{"className":589},[],[591],{"type":47,"value":592},"configure_deployer.sh",{"type":47,"value":594}," are named in\n",{"type":41,"tag":56,"props":596,"children":598},{"className":597},[],[599],{"type":47,"value":600},"docs\u002F02-00-bootstrap.md § Configure the agent",{"type":47,"value":602}," as Learn-article steps —\ndrive them only via that path; their internals are not documented here.\nOther ADO-setup scripts (",{"type":41,"tag":56,"props":604,"children":606},{"className":605},[],[607],{"type":47,"value":608},"create_devops_artifacts.sh",{"type":47,"value":84},{"type":41,"tag":56,"props":611,"children":613},{"className":612},[],[614],{"type":47,"value":615},"New-SDAFDevopsProject.ps1",{"type":47,"value":342},{"type":41,"tag":56,"props":618,"children":620},{"className":619},[],[621],{"type":47,"value":622},"New-SDAFDevopsWorkloadZone.ps1",{"type":47,"value":84},{"type":41,"tag":56,"props":625,"children":627},{"className":626},[],[628],{"type":47,"value":629},"setup_devops.ps1",{"type":47,"value":342},{"type":41,"tag":56,"props":632,"children":634},{"className":633},[],[635],{"type":47,"value":636},"Upgrade-*",{"type":47,"value":638},") are not documented here at all — do not\nreconstruct their behaviour.",{"type":41,"tag":203,"props":640,"children":641},{},[642,647,649,655],{"type":41,"tag":133,"props":643,"children":644},{},[645],{"type":47,"value":646},"Never invent parameters, roles, or variable-group values.",{"type":47,"value":648}," The\nper-variable catalogue for ",{"type":41,"tag":56,"props":650,"children":652},{"className":651},[],[653],{"type":47,"value":654},"SDAF-\u003Cenvironment>",{"type":47,"value":656}," is not exhaustively\ndocumented; state the gap, do not guess.",{"type":41,"tag":203,"props":658,"children":659},{},[660,665,667,673,675,681,683,689,691,697,699,704],{"type":41,"tag":133,"props":661,"children":662},{},[663],{"type":47,"value":664},"Credential hygiene.",{"type":47,"value":666}," Read SAP support credentials with\n",{"type":41,"tag":56,"props":668,"children":670},{"className":669},[],[671],{"type":47,"value":672},"Read-Host -AsSecureString",{"type":47,"value":674},", do not echo, and remove ",{"type":41,"tag":56,"props":676,"children":678},{"className":677},[],[679],{"type":47,"value":680},"Env:SUserName",{"type":47,"value":682}," \u002F\n",{"type":41,"tag":56,"props":684,"children":686},{"className":685},[],[687],{"type":47,"value":688},"Env:SPassword",{"type":47,"value":690}," in a ",{"type":41,"tag":56,"props":692,"children":694},{"className":693},[],[695],{"type":47,"value":696},"finally",{"type":47,"value":698}," block exactly as\n",{"type":41,"tag":56,"props":700,"children":702},{"className":701},[],[703],{"type":47,"value":252},{"type":47,"value":705}," shows.",{"type":41,"tag":203,"props":707,"children":708},{},[709,714,716,722],{"type":41,"tag":133,"props":710,"children":711},{},[712],{"type":47,"value":713},"Do not rerun a partial script blind.",{"type":47,"value":715}," Inventory what was created,\ncorrect the first failed dependency, then rerun with the same project and\ncontrol-plane names (",{"type":41,"tag":56,"props":717,"children":719},{"className":718},[],[720],{"type":47,"value":721},"docs\u002F02-00-bootstrap.md § If it fails",{"type":47,"value":480},{"type":41,"tag":203,"props":724,"children":725},{},[726,731,733,739],{"type":41,"tag":133,"props":727,"children":728},{},[729],{"type":47,"value":730},"Reuse the workload-zone code.",{"type":47,"value":732}," Same ",{"type":41,"tag":56,"props":734,"children":736},{"className":735},[],[737],{"type":47,"value":738},"$WorkloadZoneCode",{"type":47,"value":740}," updates in\nplace; a new code creates duplicate artefacts.",{"type":41,"tag":203,"props":742,"children":743},{},[744,755,757,763],{"type":41,"tag":133,"props":745,"children":746},{},[747,753],{"type":41,"tag":56,"props":748,"children":750},{"className":749},[],[751],{"type":47,"value":752},"WORKSPACES\u002FLANDSCAPE\u002F\u003Czone>\u002F\u003Czone>.tfvars",{"type":47,"value":754}," is not created here",{"type":47,"value":756}," — it\nis a prerequisite of the ",{"type":41,"tag":56,"props":758,"children":760},{"className":759},[],[761],{"type":47,"value":762},"02",{"type":47,"value":764}," deployment pipeline.",{"type":41,"tag":110,"props":766,"children":768},{"id":767},"what-this-skill-does-not-do",[769],{"type":47,"value":770},"What this skill does NOT do",{"type":41,"tag":50,"props":772,"children":773},{},[774,776,782,784,789,791,797,799,804,806,811],{"type":47,"value":775},"Choose between automated and manual paths (",{"type":41,"tag":56,"props":777,"children":779},{"className":778},[],[780],{"type":47,"value":781},"docs\u002F02-00-bootstrap.md § Manual configuration path",{"type":47,"value":783}," is a fallback the operator invokes directly); deploy the\ncontrol plane, workload zone, or any SAP system; explain individual pipeline\nparameters or run order (see ",{"type":41,"tag":56,"props":785,"children":787},{"className":786},[],[788],{"type":47,"value":161},{"type":47,"value":790},"); cover the\nGitHub Actions bootstrap (",{"type":41,"tag":56,"props":792,"children":794},{"className":793},[],[795],{"type":47,"value":796},"sap-automation-gh-bootstrap",{"type":47,"value":798},"); register the\ndeployer VM as the self-hosted agent (that happens during control-plane\ndeployment — ",{"type":41,"tag":56,"props":800,"children":802},{"className":801},[],[803],{"type":47,"value":600},{"type":47,"value":805}," points 3–4); or\nauthor \u002F debug ",{"type":41,"tag":56,"props":807,"children":809},{"className":808},[],[810],{"type":47,"value":180},{"type":47,"value":812}," itself.",{"type":41,"tag":110,"props":814,"children":816},{"id":815},"see-also",[817],{"type":47,"value":818},"See also",{"type":41,"tag":50,"props":820,"children":821},{},[822,827,829,835,837,843,844,850,852,862],{"type":41,"tag":56,"props":823,"children":825},{"className":824},[],[826],{"type":47,"value":161},{"type":47,"value":828}," — what each of the 13 pipeline wrappers does,\nthe variable groups they read, and the ",{"type":41,"tag":56,"props":830,"children":832},{"className":831},[],[833],{"type":47,"value":834},"20",{"type":47,"value":836},"\u002F",{"type":41,"tag":56,"props":838,"children":840},{"className":839},[],[841],{"type":47,"value":842},"21",{"type":47,"value":836},{"type":41,"tag":56,"props":845,"children":847},{"className":846},[],[848],{"type":47,"value":849},"22",{"type":47,"value":851}," level-up path.\n",{"type":41,"tag":73,"props":853,"children":855},{"href":854},"..\u002F..\u002Fdocs\u002Ftroubleshooting.md",[856],{"type":41,"tag":56,"props":857,"children":859},{"className":858},[],[860],{"type":47,"value":861},"docs\u002Ftroubleshooting.md",{"type":47,"value":863}," — first-triage\nfor PAT\u002Fauthorization, variable groups, service connections, and agents.",{"items":865,"total":1038},[866,885,904,918,931,949,960,973,983,996,1009,1025],{"slug":867,"name":867,"fn":868,"description":869,"org":870,"tags":871,"stars":882,"repoUrl":883,"updatedAt":884},"azure-arg-external-evaluation-policy-author","author and test Azure Resource Graph policies","Use when the user wants to author, design, or test an Azure Policy that queries Azure Resource Graph (ARG) at request-time — i.e. a policy whose deny\u002Faudit decision depends on data from elsewhere in the subscription (sibling\u002Fparent resource state, RG-wide invariants, multi-hop relationships, etc.). Formally called Azure Policy External Evaluation; sometimes referred to colloquially as \"Invoke\". Drives an iterative KQL co-design loop against the user's real subscription via `az graph query`, then emits a policy definition, assignment, `.http` test flow, and an `EXPLANATION.md` companion. Read-only; never provisions anything.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[872,873,876,879],{"name":11,"slug":8,"type":14},{"name":874,"slug":875,"type":14},"Compliance","compliance",{"name":877,"slug":878,"type":14},"Governance","governance",{"name":880,"slug":881,"type":14},"Policy","policy",1689,"https:\u002F\u002Fgithub.com\u002FAzure\u002Fazure-policy","2026-07-12T08:17:48.378432",{"slug":886,"name":886,"fn":887,"description":888,"org":889,"tags":890,"stars":901,"repoUrl":902,"updatedAt":903},"azure-blueprints-migration","migrate Azure Blueprints to Template Specs","Use when a user needs to migrate off Azure Blueprints (definitions and\u002For assignments) to Template Specs and Deployment Stacks before the January 31, 2027 retirement. Covers inventory, export, conversion to Bicep, policy decoupling, Template Spec publishing, Deployment Stack deployment with deny-settings, validation, and cutover.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[891,892,895,898],{"name":11,"slug":8,"type":14},{"name":893,"slug":894,"type":14},"Deployment","deployment",{"name":896,"slug":897,"type":14},"Infrastructure as Code","infrastructure-as-code",{"name":899,"slug":900,"type":14},"Migration","migration",261,"https:\u002F\u002Fgithub.com\u002FAzure\u002Fazure-blueprints","2026-08-20T03:28:18.136156",{"slug":905,"name":905,"fn":906,"description":907,"org":908,"tags":909,"stars":915,"repoUrl":916,"updatedAt":917},"sdaf-bom-selection","select SAP Bill of Materials","Pick the right SDAF BOM for a target SAP product \u002F release \u002F DB platform \u002F version \u002F kernel \u002F topology. Explains where BOMs live in the samples repo (`SAP\u002F` for whole products, `BOM\u002F` for components), decodes the `ms`, `v####`, and `latest` suffix conventions, points at the compatibility guardrails (`supportedPlatforms`, `supportedDBVersions`, `supportedKernels`), and reminds the operator that the download flow needs four explicit BOM keys in `sap-parameters.yaml`. Use when a user says \"which BOM do I use\", \"product BOM vs component BOM\", \"SAP samples BOM catalog\", \"BOM_CATALOG\", \"S4\u002F2023 BOM\", \"HANA BOM\", or \"how do I pick a BOM for HANA\u002FOracle\u002FDB2\u002FASE\". Do NOT use to author a new BOM, to acquire media (`sdaf-media-acquisition`), or to troubleshoot a checksum \u002F 404 (`sdaf-media-diagnostics`).\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[910,911,914],{"name":11,"slug":8,"type":14},{"name":912,"slug":913,"type":14},"Configuration","configuration",{"name":22,"slug":23,"type":14},143,"https:\u002F\u002Fgithub.com\u002FAzure\u002Fsap-automation","2026-09-02T07:47:45.597063",{"slug":919,"name":919,"fn":920,"description":921,"org":922,"tags":923,"stars":915,"repoUrl":916,"updatedAt":930},"sdaf-control-plane-bootstrap","deploy SDAF control plane infrastructure","Deploy the SDAF control plane locally: prepare DEPLOYER and LIBRARY tfvars, review the plan, run `deploy_controlplane.sh` per `docs\u002Flocal\u002F03-00-control-plane.md § Run`, and validate the deployer + library + state hand-off. Grounded in `docs\u002Flocal\u002F03-00-control-plane.md`. Use when a user says \"deploy the SDAF control plane\", \"run deploy_controlplane.sh\", \"bootstrap SDAF from an empty subscription\", \"install the deployer\" or \"create the SAP library\". Do NOT use for workload zone (see sdaf-workload-zone), SAP system (see sdaf-sap-system), removal (`sdaf-safe-removal`), or Azure Government \u002F sovereign-cloud deltas (`sdaf-sovereign-cloud`).\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[924,925,926,929],{"name":11,"slug":8,"type":14},{"name":893,"slug":894,"type":14},{"name":927,"slug":928,"type":14},"Infrastructure","infrastructure",{"name":22,"slug":23,"type":14},"2026-09-02T07:46:51.573641",{"slug":932,"name":932,"fn":933,"description":934,"org":935,"tags":936,"stars":915,"repoUrl":916,"updatedAt":948},"sdaf-failure-triage","triage failed SAP automation runs","Triage a failed or suspicious SDAF run: distinguish a real failure from a green no-op or a clean plan reported as failure, map the observed symptom to a documented cause in `docs\u002Flocal\u002Ftroubleshooting.md`, and hand off to the stage-owning skill for retry. Use when a user says \"SDAF run failed\", \"my deploy exited non-zero\", \"the plan was clean but exit 1\", \"the run said success but nothing was deployed\", \"state lock error\", \"unexpected replacement\", \"control plane stopped partway\", \"generated hosts.yaml missing\", \"workload-zone private endpoint failure\", \"workload-zone subnet policy failure\", or \"SDAF exit 2\". Do NOT use to actually deploy or to redesign the workspace layout.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[937,938,941,944,945],{"name":11,"slug":8,"type":14},{"name":939,"slug":940,"type":14},"Diagnostics","diagnostics",{"name":942,"slug":943,"type":14},"Operations","operations",{"name":22,"slug":23,"type":14},{"name":946,"slug":947,"type":14},"Triage","triage","2026-09-02T07:47:40.607437",{"slug":950,"name":950,"fn":951,"description":952,"org":953,"tags":954,"stars":915,"repoUrl":916,"updatedAt":959},"sdaf-ha-diagnostics","diagnose SDAF high-availability cluster failures","Diagnose a live or recently failed SDAF high-availability cluster without changing cluster state. Start read-first: capture `crm status full` or `pcs status --full`, inspect SBD or fencing evidence, confirm current resource placement, and reuse existing quality-assurance or HCMT artifacts. Grounded in `docs\u002Flocal\u002F07-10-quality-assurance.md`, the shipped Pacemaker role vars\u002Ftasks, and the SAP Automation QA setup role. Use when a user says \"diagnose my HANA failover\", \"crm status\", \"pcs status\", \"check fencing\", \"why is the SCS\u002FERS cluster unhealthy\", \"offline_validation\u002Fcib\", or \"review an HCMT result zip\". Do NOT use for pre-deploy topology or design choices (see `sdaf-ha-topology`), fresh installation\u002Fdeploy, or disruptive failover\u002Ffencing exercises (see `sdaf-quality-assurance`).\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[955,956,957,958],{"name":11,"slug":8,"type":14},{"name":939,"slug":940,"type":14},{"name":942,"slug":943,"type":14},{"name":22,"slug":23,"type":14},"2026-09-02T07:48:04.154501",{"slug":961,"name":961,"fn":962,"description":963,"org":964,"tags":965,"stars":915,"repoUrl":916,"updatedAt":972},"sdaf-ha-topology","design high-availability SAP topologies","Choose the documented SDAF high-availability design before SAP-system deployment. Use when a user asks which HA topology to deploy, whether to use AFA or SBD, AFS or ANF, HANA scale-up or scale-out, whether ANGI is allowed, or which HA inputs must be set before deployment. Ground answers in the current support matrix, Ansible roles, sample tfvars, and validation logic. Do NOT use for live cluster diagnosis (sdaf-ha-diagnostics) or for running the installers (sdaf-sap-installation).\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[966,969,970,971],{"name":967,"slug":968,"type":14},"Architecture","architecture",{"name":11,"slug":8,"type":14},{"name":927,"slug":928,"type":14},{"name":22,"slug":23,"type":14},"2026-09-02T07:47:43.405138",{"slug":974,"name":974,"fn":975,"description":976,"org":977,"tags":978,"stars":915,"repoUrl":916,"updatedAt":982},"sdaf-media-acquisition","acquire SAP installation media","Acquire approved SAP media into the SDAF library after SAP-system infrastructure exists. Drives local `deploy\u002Fansible\u002Fdownload_menu.sh` per `docs\u002Flocal\u002F06-00-software-and-installation.md § Download software`, enforces the documented `BOM_CATALOG` root and the four required `sap-parameters.yaml` BOM keys (`application_bom_name`, `database_bom_name`, `sap_kernel_bom_name`, `save_bom_as`), and explains the documented download and validation flow. Use for \"download SAP media\", \"run download_menu.sh\", \"acquire software into the library\", \"BOM Downloader\", \"BOM_CATALOG\", or \"assemble application\u002Fdatabase\u002Fkernel BOMs for download\". Do NOT use to choose a BOM, troubleshoot a failed download, or run installation playbooks.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[979,980,981],{"name":11,"slug":8,"type":14},{"name":942,"slug":943,"type":14},{"name":22,"slug":23,"type":14},"2026-09-02T07:46:44.504107",{"slug":984,"name":984,"fn":985,"description":986,"org":987,"tags":988,"stars":915,"repoUrl":916,"updatedAt":995},"sdaf-media-diagnostics","diagnose SDAF media and BOM processing","Diagnose SDAF software-download and BOM-processing failures after a BOM is already selected. Covers the documented local media path, SAP download, storage-account upload\u002Fdownload, checksum validation, and `SAPCAR` \u002F `.EXE` extraction. Use when a user says \"download_menu failed\", \"BOM downloader 404\", \"missing archive\", \"checksum mismatch\", \"SAPCAR failed\", \"bom-processing-done missing\", or \"my SPS07 media run can't find a file\". Do NOT use to choose a BOM (see `sdaf-bom-selection`), to run a clean first-time media download with no failure, or to diagnose a later non-media install failure.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[989,990,991,992],{"name":11,"slug":8,"type":14},{"name":939,"slug":940,"type":14},{"name":22,"slug":23,"type":14},{"name":993,"slug":994,"type":14},"Storage","storage","2026-09-02T07:48:06.369058",{"slug":997,"name":997,"fn":998,"description":999,"org":1000,"tags":1001,"stars":915,"repoUrl":916,"updatedAt":1008},"sdaf-orientation-and-surface","orient users to SDAF architecture","Orient a newcomer to the SAP Deployment Automation Framework (SDAF): explain the spine (control plane → workload zone → SAP system → software → install → operate\u002Fremove), summarise the three execution surfaces (Local, Azure DevOps, GitHub Actions), and print the install command for the matching surface bootstrap plugin — as documented in this repository's `docs\u002FPLUGINS.md` — so the operator can run it manually. Use when a user says \"what is SDAF\", \"how is SDAF structured\", \"where do I start with SDAF\", \"which surface should I use\", \"SDAF Local vs ADO vs GitHub\", \"workstation vs Azure Pipelines vs GitHub workflows\", \"how do I install the SDAF ADO\u002FGitHub plugin\", or \"I'm new to SDAF\". Do NOT use for readiness pre-flight (see sdaf-readiness-check), workspace\u002Ftfvars layout (see sdaf-workspace-and-tfvars), or troubleshooting a failed run (see sdaf-failure-triage).\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1002,1003,1004,1007],{"name":967,"slug":968,"type":14},{"name":11,"slug":8,"type":14},{"name":1005,"slug":1006,"type":14},"Documentation","documentation",{"name":22,"slug":23,"type":14},"2026-09-02T07:46:52.116557",{"slug":1010,"name":1010,"fn":1011,"description":1012,"org":1013,"tags":1014,"stars":915,"repoUrl":916,"updatedAt":1024},"sdaf-plan-and-test-semantics","manage SDAF plan and test semantics","Explain SDAF plan-only \u002F test \u002F apply semantics without pretending they are universal. Compares the documented Local commands, Azure DevOps wrapper pipelines, and GitHub Actions workflows for control plane, workload zone, and SAP system: local stage commands show Terraform plans and then apply after approval; ADO\u002FGitHub workload-zone and SAP-system test runs stop after the plan; the current hosted control-plane test options do not provide a plan-only run. Use when a user says \"what does test do in SDAF\", \"is this a real dry run\", \"plan-only vs apply\", \"workflow 01 dry-run\", \"pipeline 02 test\", or \"TEST_ONLY\". Do NOT use to actually deploy a stage or to triage a failed run (see sdaf-control-plane-bootstrap \u002F sdaf-workload-zone \u002F sdaf-sap-system \u002F sdaf-failure-triage).\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1015,1016,1017,1018,1021],{"name":16,"slug":17,"type":14},{"name":11,"slug":8,"type":14},{"name":19,"slug":20,"type":14},{"name":1019,"slug":1020,"type":14},"CI\u002FCD","ci-cd",{"name":1022,"slug":1023,"type":14},"GitHub Actions","github-actions","2026-09-02T07:48:08.951811",{"slug":1026,"name":1026,"fn":1027,"description":1028,"org":1029,"tags":1030,"stars":915,"repoUrl":916,"updatedAt":1037},"sdaf-quality-assurance","validate deployed SDAF SAP systems","Validate a deployed SDAF SAP system through the SDAF-owned QA entry points: the local quality-assurance menu and the documented Azure DevOps pipeline 13 path. Choose configuration checks vs functional tests, apply `TEST_GROUPS` \u002F `TEST_CASES` safely, interpret `quality_assurance\u002F` and `logs\u002F`, and enforce the documented boundary that the GitHub Actions wrapper is still pending. Use when a user says \"run quality assurance\", \"run configuration checks\", \"pipeline 13 QA\", \"offline HA validation\", or \"why does the report say No test results found\". Do NOT use to deploy the SAP system or generate `sap-parameters.yaml` \u002F `\u003CSID>_hosts.yaml` (see `sdaf-sap-system`), or for a generic failed-run report with no QA-stage context (see `sdaf-failure-triage`).\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1031,1032,1033,1036],{"name":16,"slug":17,"type":14},{"name":11,"slug":8,"type":14},{"name":1034,"slug":1035,"type":14},"Quality Assurance","quality-assurance",{"name":22,"slug":23,"type":14},"2026-09-02T07:46:49.932123",145,{"items":1040,"total":1058},[1041,1051],{"slug":161,"name":161,"fn":1042,"description":1043,"org":1044,"tags":1045,"stars":24,"repoUrl":25,"updatedAt":1050},"reference SDAF Azure DevOps pipelines","Reference catalogue of the 13 Azure DevOps pipeline wrappers that ship in\nsap-automation-bootstrap\u002Fpipelines: what each wrapper does, its documented\nparameters and preconditions, which variable groups it reads\n(SDAF-General, SDAF-\u003Ccontrol-plane>, SDAF-\u003Cworkload-environment>), and the\ndocumented 20 \u002F 21 \u002F 22 self-update (\"level-up\") path. Grounded in\ndocs\u002Fpipeline-reference.md and docs\u002F07-00-operations.md. Use when an\noperator says: \"which pipeline should I run for X?\", \"what does pipeline\n01\u002F02\u002F03\u002F04\u002F05\u002F07\u002F10\u002F11\u002F12\u002F20\u002F21\u002F22 do?\", \"what parameters does the\nworkload-zone pipeline take?\", \"what variable group does 05 read?\",\n\"explain 20 vs 21 vs 22\", \"how do I level up SDAF pipelines?\". NOT for\nstanding the ADO project up in the first place (see\nsdaf-ado-project-bootstrap), for running a deployment, or for GitHub\nActions workflows.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1046,1047,1048,1049],{"name":11,"slug":8,"type":14},{"name":19,"slug":20,"type":14},{"name":1005,"slug":1006,"type":14},{"name":22,"slug":23,"type":14},"2026-09-02T07:46:50.474067",{"slug":4,"name":4,"fn":5,"description":6,"org":1052,"tags":1053,"stars":24,"repoUrl":25,"updatedAt":26},{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1054,1055,1056,1057],{"name":16,"slug":17,"type":14},{"name":11,"slug":8,"type":14},{"name":19,"slug":20,"type":14},{"name":22,"slug":23,"type":14},2]