[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-azure-sdaf-ha-topology":3,"mdc-k5fgp3-key":35,"related-repo-azure-sdaf-ha-topology":640,"related-org-azure-sdaf-ha-topology":726},{"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-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},"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},"Architecture","architecture",{"name":19,"slug":20,"type":14},"SAP","sap",{"name":22,"slug":23,"type":14},"Infrastructure","infrastructure",143,"https:\u002F\u002Fgithub.com\u002FAzure\u002Fsap-automation","2026-09-02T07:47:43.405138","MIT",173,[],{"repoUrl":25,"stars":24,"forks":28,"topics":31,"description":32},[],"This is the repository supporting the SAP deployment automation framework on Azure","https:\u002F\u002Fgithub.com\u002FAzure\u002Fsap-automation\u002Ftree\u002FHEAD\u002Fskills\u002Fsdaf-ha-topology","---\nname: sdaf-ha-topology\ndescription: >\n  Choose the documented SDAF high-availability design before SAP-system\n  deployment. Use when a user asks which HA topology to deploy, whether to use\n  AFA or SBD, AFS or ANF, HANA scale-up or scale-out, whether ANGI is allowed,\n  or which HA inputs must be set before deployment. Ground answers in the\n  current support matrix, Ansible roles, sample tfvars, and validation logic.\n  Do NOT use for live cluster diagnosis (sdaf-ha-diagnostics) or for running\n  the installers (sdaf-sap-installation).\nallowed-tools: shell\nlicense: MIT\n---\n\n# SDAF HA Topology\n\nContext-primer for **pre-deploy** HA design. Keep this skill short and route to\n[`references\u002Ftopology-decision-guide.md`](references\u002Ftopology-decision-guide.md)\nfor the detailed OS\u002FDB\u002Fstorage matrices, sample-backed examples, and source\nmap.\n\n## When to invoke\n\nTrigger on:\n\n- \"Which SDAF HA topology should I use?\"\n- \"AFA or shared-disk \u002F iSCSI quorum?\"\n- \"AFS or ANF for this SAP HA design?\"\n- \"Should HANA stay scale-up or move to scale-out?\"\n- \"Can I enable SAPHanaSR-angi on this OS release?\"\n- \"What HA inputs do I need in system tfvars before deployment?\"\n\nDo NOT trigger on:\n\n- a live cluster failure, fencing event, or `crm` \u002F `pcs` diagnosis — use\n  `sdaf-ha-diagnostics`\n- running numbered install stages or partial-install recovery — use\n  `sdaf-sap-installation`\n- generic SAP-system Terraform deployment without an HA design question — use\n  `sdaf-sap-system`\n\n## Preconditions\n\nBefore answering, know or ask for:\n\n- target operating system and version\n- target database platform\n- whether HA is required for central services, the database tier, or both\n- whether the question is design-time or an already-deployed cluster problem\n\n## Decision loop\n\n1. **Confirm the support boundary first.** Start with\n   [`docs\u002Fsupportability.md`](..\u002F..\u002Fdocs\u002Fsupportability.md). A listed OS,\n   database, or storage option does **not** make every cross-combination valid.\n   If the requested combination is not explicitly backed by current docs and\n   code, say docs are silent and stop.\n2. **Split the question into layers.** Treat HA as separate design choices for:\n   - SAP central services: `scs_server_count`, `scs_high_availability`,\n     `scs_cluster_type`\n   - database tier: `database_high_availability`, `database_cluster_type`, and\n     for HANA `database_HANA_use_scaleout_scenario`\n3. **Confirm the documented platform path.** Use\n   `docs\u002Fsupportability.md` and the current SAP-system input documentation.\n   Do not infer that every listed database has an SDAF-managed HA topology.\n4. **Choose quorum \u002F fencing deliberately.** The tfvar contract exposes `AFA`,\n   `ASD`, and `ISCSI` for both SCS and DB tiers. AFA needs fencing credentials\n   unless `use_msi_for_clusters = true`. ASD \u002F ISCSI take the SBD path, so the\n   OS release must satisfy the current role gates before cluster creation.\n5. **Choose shared storage deliberately.** Use current docs and mount logic:\n   - `AFS` for shared SAP file systems only\n   - `ANF` for applicable shared and database file systems\n   - custom `NFS` as organization-owned design, not a Microsoft-owned reference\n6. **Handle HANA-only forks explicitly.** For HANA, decide scale-up vs\n   scale-out and, separately, whether `use_saphanasr_angi` is allowed on the\n   target OS. Do not apply scale-out or ANGI guidance to Oracle, DB2, ASE, or\n   SQL Server.\n7. **Route rather than guess.** If the user is asking how to deploy the chosen\n   design, hand off to `sdaf-sap-system`. If the user is asking why an existing\n   cluster failed, hand off to `sdaf-ha-diagnostics`.\n\n## Validate before deployment\n\nUse the documented SAP-system validation step as the pre-deploy gate. For HA\nanswers, make sure the selected path can supply:\n\n- cluster-aware base inputs: `database_high_availability`,\n  `database_cluster_type`, `scs_high_availability`, `scs_cluster_type`,\n  `use_msi_for_clusters`, `platform`\n- for SCS HA: shared storage, `NFS_provider`, and central-services\n  load-balancer inputs\n- for AFA without MSI: fencing client ID, password, subscription, and tenant\n- for HANA \u002F DB2 AFA database HA: the database load-balancer IP\n- for HANA scale-out: standby \u002F observer \u002F shared-storage inputs that match the\n  selected path\n\n## Hard safety rules\n\n- Do not infer support from one sample, one BOM, or one tfvar alone.\n- Do not promise an ASE database-HA topology from the current DB-HA playbook.\n- Do not apply HANA-only scale-out or ANGI guidance to non-HANA databases.\n- Do not use Azure Files NFS as a database-file-system answer.\n- Do not generalize Pacemaker validation guidance to Windows clustering.\n- If docs, samples, and current roles disagree, stop and call out the mismatch.\n\n## Hand-off\n\n- deploy the chosen infrastructure path -> `sdaf-sap-system`\n- run OS \u002F DB \u002F SAP install stages -> `sdaf-sap-installation`\n- diagnose a live cluster or fencing issue -> `sdaf-ha-diagnostics`\n- run post-deploy HA checks -> `sdaf-quality-assurance`\n",{"data":36,"body":38},{"name":4,"description":6,"allowed-tools":37,"license":27},"shell",{"type":39,"children":40},"root",[41,49,76,83,88,123,128,180,186,191,214,220,467,473,478,551,557,590,596],{"type":42,"tag":43,"props":44,"children":45},"element","h1",{"id":4},[46],{"type":47,"value":48},"text","SDAF HA Topology",{"type":42,"tag":50,"props":51,"children":52},"p",{},[53,55,61,63,74],{"type":47,"value":54},"Context-primer for ",{"type":42,"tag":56,"props":57,"children":58},"strong",{},[59],{"type":47,"value":60},"pre-deploy",{"type":47,"value":62}," HA design. Keep this skill short and route to\n",{"type":42,"tag":64,"props":65,"children":67},"a",{"href":66},"references\u002Ftopology-decision-guide.md",[68],{"type":42,"tag":69,"props":70,"children":72},"code",{"className":71},[],[73],{"type":47,"value":66},{"type":47,"value":75},"\nfor the detailed OS\u002FDB\u002Fstorage matrices, sample-backed examples, and source\nmap.",{"type":42,"tag":77,"props":78,"children":80},"h2",{"id":79},"when-to-invoke",[81],{"type":47,"value":82},"When to invoke",{"type":42,"tag":50,"props":84,"children":85},{},[86],{"type":47,"value":87},"Trigger on:",{"type":42,"tag":89,"props":90,"children":91},"ul",{},[92,98,103,108,113,118],{"type":42,"tag":93,"props":94,"children":95},"li",{},[96],{"type":47,"value":97},"\"Which SDAF HA topology should I use?\"",{"type":42,"tag":93,"props":99,"children":100},{},[101],{"type":47,"value":102},"\"AFA or shared-disk \u002F iSCSI quorum?\"",{"type":42,"tag":93,"props":104,"children":105},{},[106],{"type":47,"value":107},"\"AFS or ANF for this SAP HA design?\"",{"type":42,"tag":93,"props":109,"children":110},{},[111],{"type":47,"value":112},"\"Should HANA stay scale-up or move to scale-out?\"",{"type":42,"tag":93,"props":114,"children":115},{},[116],{"type":47,"value":117},"\"Can I enable SAPHanaSR-angi on this OS release?\"",{"type":42,"tag":93,"props":119,"children":120},{},[121],{"type":47,"value":122},"\"What HA inputs do I need in system tfvars before deployment?\"",{"type":42,"tag":50,"props":124,"children":125},{},[126],{"type":47,"value":127},"Do NOT trigger on:",{"type":42,"tag":89,"props":129,"children":130},{},[131,158,169],{"type":42,"tag":93,"props":132,"children":133},{},[134,136,142,144,150,152],{"type":47,"value":135},"a live cluster failure, fencing event, or ",{"type":42,"tag":69,"props":137,"children":139},{"className":138},[],[140],{"type":47,"value":141},"crm",{"type":47,"value":143}," \u002F ",{"type":42,"tag":69,"props":145,"children":147},{"className":146},[],[148],{"type":47,"value":149},"pcs",{"type":47,"value":151}," diagnosis — use\n",{"type":42,"tag":69,"props":153,"children":155},{"className":154},[],[156],{"type":47,"value":157},"sdaf-ha-diagnostics",{"type":42,"tag":93,"props":159,"children":160},{},[161,163],{"type":47,"value":162},"running numbered install stages or partial-install recovery — use\n",{"type":42,"tag":69,"props":164,"children":166},{"className":165},[],[167],{"type":47,"value":168},"sdaf-sap-installation",{"type":42,"tag":93,"props":170,"children":171},{},[172,174],{"type":47,"value":173},"generic SAP-system Terraform deployment without an HA design question — use\n",{"type":42,"tag":69,"props":175,"children":177},{"className":176},[],[178],{"type":47,"value":179},"sdaf-sap-system",{"type":42,"tag":77,"props":181,"children":183},{"id":182},"preconditions",[184],{"type":47,"value":185},"Preconditions",{"type":42,"tag":50,"props":187,"children":188},{},[189],{"type":47,"value":190},"Before answering, know or ask for:",{"type":42,"tag":89,"props":192,"children":193},{},[194,199,204,209],{"type":42,"tag":93,"props":195,"children":196},{},[197],{"type":47,"value":198},"target operating system and version",{"type":42,"tag":93,"props":200,"children":201},{},[202],{"type":47,"value":203},"target database platform",{"type":42,"tag":93,"props":205,"children":206},{},[207],{"type":47,"value":208},"whether HA is required for central services, the database tier, or both",{"type":42,"tag":93,"props":210,"children":211},{},[212],{"type":47,"value":213},"whether the question is design-time or an already-deployed cluster problem",{"type":42,"tag":77,"props":215,"children":217},{"id":216},"decision-loop",[218],{"type":47,"value":219},"Decision loop",{"type":42,"tag":221,"props":222,"children":223},"ol",{},[224,253,319,336,377,425,443],{"type":42,"tag":93,"props":225,"children":226},{},[227,232,234,244,246,251],{"type":42,"tag":56,"props":228,"children":229},{},[230],{"type":47,"value":231},"Confirm the support boundary first.",{"type":47,"value":233}," Start with\n",{"type":42,"tag":64,"props":235,"children":237},{"href":236},"..\u002F..\u002Fdocs\u002Fsupportability.md",[238],{"type":42,"tag":69,"props":239,"children":241},{"className":240},[],[242],{"type":47,"value":243},"docs\u002Fsupportability.md",{"type":47,"value":245},". A listed OS,\ndatabase, or storage option does ",{"type":42,"tag":56,"props":247,"children":248},{},[249],{"type":47,"value":250},"not",{"type":47,"value":252}," make every cross-combination valid.\nIf the requested combination is not explicitly backed by current docs and\ncode, say docs are silent and stop.",{"type":42,"tag":93,"props":254,"children":255},{},[256,261,263],{"type":42,"tag":56,"props":257,"children":258},{},[259],{"type":47,"value":260},"Split the question into layers.",{"type":47,"value":262}," Treat HA as separate design choices for:\n",{"type":42,"tag":89,"props":264,"children":265},{},[266,293],{"type":42,"tag":93,"props":267,"children":268},{},[269,271,277,279,285,287],{"type":47,"value":270},"SAP central services: ",{"type":42,"tag":69,"props":272,"children":274},{"className":273},[],[275],{"type":47,"value":276},"scs_server_count",{"type":47,"value":278},", ",{"type":42,"tag":69,"props":280,"children":282},{"className":281},[],[283],{"type":47,"value":284},"scs_high_availability",{"type":47,"value":286},",\n",{"type":42,"tag":69,"props":288,"children":290},{"className":289},[],[291],{"type":47,"value":292},"scs_cluster_type",{"type":42,"tag":93,"props":294,"children":295},{},[296,298,304,305,311,313],{"type":47,"value":297},"database tier: ",{"type":42,"tag":69,"props":299,"children":301},{"className":300},[],[302],{"type":47,"value":303},"database_high_availability",{"type":47,"value":278},{"type":42,"tag":69,"props":306,"children":308},{"className":307},[],[309],{"type":47,"value":310},"database_cluster_type",{"type":47,"value":312},", and\nfor HANA ",{"type":42,"tag":69,"props":314,"children":316},{"className":315},[],[317],{"type":47,"value":318},"database_HANA_use_scaleout_scenario",{"type":42,"tag":93,"props":320,"children":321},{},[322,327,329,334],{"type":42,"tag":56,"props":323,"children":324},{},[325],{"type":47,"value":326},"Confirm the documented platform path.",{"type":47,"value":328}," Use\n",{"type":42,"tag":69,"props":330,"children":332},{"className":331},[],[333],{"type":47,"value":243},{"type":47,"value":335}," and the current SAP-system input documentation.\nDo not infer that every listed database has an SDAF-managed HA topology.",{"type":42,"tag":93,"props":337,"children":338},{},[339,344,346,352,353,359,361,367,369,375],{"type":42,"tag":56,"props":340,"children":341},{},[342],{"type":47,"value":343},"Choose quorum \u002F fencing deliberately.",{"type":47,"value":345}," The tfvar contract exposes ",{"type":42,"tag":69,"props":347,"children":349},{"className":348},[],[350],{"type":47,"value":351},"AFA",{"type":47,"value":286},{"type":42,"tag":69,"props":354,"children":356},{"className":355},[],[357],{"type":47,"value":358},"ASD",{"type":47,"value":360},", and ",{"type":42,"tag":69,"props":362,"children":364},{"className":363},[],[365],{"type":47,"value":366},"ISCSI",{"type":47,"value":368}," for both SCS and DB tiers. AFA needs fencing credentials\nunless ",{"type":42,"tag":69,"props":370,"children":372},{"className":371},[],[373],{"type":47,"value":374},"use_msi_for_clusters = true",{"type":47,"value":376},". ASD \u002F ISCSI take the SBD path, so the\nOS release must satisfy the current role gates before cluster creation.",{"type":42,"tag":93,"props":378,"children":379},{},[380,385,387],{"type":42,"tag":56,"props":381,"children":382},{},[383],{"type":47,"value":384},"Choose shared storage deliberately.",{"type":47,"value":386}," Use current docs and mount logic:\n",{"type":42,"tag":89,"props":388,"children":389},{},[390,401,412],{"type":42,"tag":93,"props":391,"children":392},{},[393,399],{"type":42,"tag":69,"props":394,"children":396},{"className":395},[],[397],{"type":47,"value":398},"AFS",{"type":47,"value":400}," for shared SAP file systems only",{"type":42,"tag":93,"props":402,"children":403},{},[404,410],{"type":42,"tag":69,"props":405,"children":407},{"className":406},[],[408],{"type":47,"value":409},"ANF",{"type":47,"value":411}," for applicable shared and database file systems",{"type":42,"tag":93,"props":413,"children":414},{},[415,417,423],{"type":47,"value":416},"custom ",{"type":42,"tag":69,"props":418,"children":420},{"className":419},[],[421],{"type":47,"value":422},"NFS",{"type":47,"value":424}," as organization-owned design, not a Microsoft-owned reference",{"type":42,"tag":93,"props":426,"children":427},{},[428,433,435,441],{"type":42,"tag":56,"props":429,"children":430},{},[431],{"type":47,"value":432},"Handle HANA-only forks explicitly.",{"type":47,"value":434}," For HANA, decide scale-up vs\nscale-out and, separately, whether ",{"type":42,"tag":69,"props":436,"children":438},{"className":437},[],[439],{"type":47,"value":440},"use_saphanasr_angi",{"type":47,"value":442}," is allowed on the\ntarget OS. Do not apply scale-out or ANGI guidance to Oracle, DB2, ASE, or\nSQL Server.",{"type":42,"tag":93,"props":444,"children":445},{},[446,451,453,458,460,465],{"type":42,"tag":56,"props":447,"children":448},{},[449],{"type":47,"value":450},"Route rather than guess.",{"type":47,"value":452}," If the user is asking how to deploy the chosen\ndesign, hand off to ",{"type":42,"tag":69,"props":454,"children":456},{"className":455},[],[457],{"type":47,"value":179},{"type":47,"value":459},". If the user is asking why an existing\ncluster failed, hand off to ",{"type":42,"tag":69,"props":461,"children":463},{"className":462},[],[464],{"type":47,"value":157},{"type":47,"value":466},".",{"type":42,"tag":77,"props":468,"children":470},{"id":469},"validate-before-deployment",[471],{"type":47,"value":472},"Validate before deployment",{"type":42,"tag":50,"props":474,"children":475},{},[476],{"type":47,"value":477},"Use the documented SAP-system validation step as the pre-deploy gate. For HA\nanswers, make sure the selected path can supply:",{"type":42,"tag":89,"props":479,"children":480},{},[481,523,536,541,546],{"type":42,"tag":93,"props":482,"children":483},{},[484,486,491,492,497,498,503,504,509,510,516,517],{"type":47,"value":485},"cluster-aware base inputs: ",{"type":42,"tag":69,"props":487,"children":489},{"className":488},[],[490],{"type":47,"value":303},{"type":47,"value":286},{"type":42,"tag":69,"props":493,"children":495},{"className":494},[],[496],{"type":47,"value":310},{"type":47,"value":278},{"type":42,"tag":69,"props":499,"children":501},{"className":500},[],[502],{"type":47,"value":284},{"type":47,"value":278},{"type":42,"tag":69,"props":505,"children":507},{"className":506},[],[508],{"type":47,"value":292},{"type":47,"value":286},{"type":42,"tag":69,"props":511,"children":513},{"className":512},[],[514],{"type":47,"value":515},"use_msi_for_clusters",{"type":47,"value":278},{"type":42,"tag":69,"props":518,"children":520},{"className":519},[],[521],{"type":47,"value":522},"platform",{"type":42,"tag":93,"props":524,"children":525},{},[526,528,534],{"type":47,"value":527},"for SCS HA: shared storage, ",{"type":42,"tag":69,"props":529,"children":531},{"className":530},[],[532],{"type":47,"value":533},"NFS_provider",{"type":47,"value":535},", and central-services\nload-balancer inputs",{"type":42,"tag":93,"props":537,"children":538},{},[539],{"type":47,"value":540},"for AFA without MSI: fencing client ID, password, subscription, and tenant",{"type":42,"tag":93,"props":542,"children":543},{},[544],{"type":47,"value":545},"for HANA \u002F DB2 AFA database HA: the database load-balancer IP",{"type":42,"tag":93,"props":547,"children":548},{},[549],{"type":47,"value":550},"for HANA scale-out: standby \u002F observer \u002F shared-storage inputs that match the\nselected path",{"type":42,"tag":77,"props":552,"children":554},{"id":553},"hard-safety-rules",[555],{"type":47,"value":556},"Hard safety rules",{"type":42,"tag":89,"props":558,"children":559},{},[560,565,570,575,580,585],{"type":42,"tag":93,"props":561,"children":562},{},[563],{"type":47,"value":564},"Do not infer support from one sample, one BOM, or one tfvar alone.",{"type":42,"tag":93,"props":566,"children":567},{},[568],{"type":47,"value":569},"Do not promise an ASE database-HA topology from the current DB-HA playbook.",{"type":42,"tag":93,"props":571,"children":572},{},[573],{"type":47,"value":574},"Do not apply HANA-only scale-out or ANGI guidance to non-HANA databases.",{"type":42,"tag":93,"props":576,"children":577},{},[578],{"type":47,"value":579},"Do not use Azure Files NFS as a database-file-system answer.",{"type":42,"tag":93,"props":581,"children":582},{},[583],{"type":47,"value":584},"Do not generalize Pacemaker validation guidance to Windows clustering.",{"type":42,"tag":93,"props":586,"children":587},{},[588],{"type":47,"value":589},"If docs, samples, and current roles disagree, stop and call out the mismatch.",{"type":42,"tag":77,"props":591,"children":593},{"id":592},"hand-off",[594],{"type":47,"value":595},"Hand-off",{"type":42,"tag":89,"props":597,"children":598},{},[599,609,619,629],{"type":42,"tag":93,"props":600,"children":601},{},[602,604],{"type":47,"value":603},"deploy the chosen infrastructure path -> ",{"type":42,"tag":69,"props":605,"children":607},{"className":606},[],[608],{"type":47,"value":179},{"type":42,"tag":93,"props":610,"children":611},{},[612,614],{"type":47,"value":613},"run OS \u002F DB \u002F SAP install stages -> ",{"type":42,"tag":69,"props":615,"children":617},{"className":616},[],[618],{"type":47,"value":168},{"type":42,"tag":93,"props":620,"children":621},{},[622,624],{"type":47,"value":623},"diagnose a live cluster or fencing issue -> ",{"type":42,"tag":69,"props":625,"children":627},{"className":626},[],[628],{"type":47,"value":157},{"type":42,"tag":93,"props":630,"children":631},{},[632,634],{"type":47,"value":633},"run post-deploy HA checks -> ",{"type":42,"tag":69,"props":635,"children":637},{"className":636},[],[638],{"type":47,"value":639},"sdaf-quality-assurance",{"items":641,"total":725},[642,654,667,685,695,702,712],{"slug":643,"name":643,"fn":644,"description":645,"org":646,"tags":647,"stars":24,"repoUrl":25,"updatedAt":653},"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},[648,649,652],{"name":11,"slug":8,"type":14},{"name":650,"slug":651,"type":14},"Configuration","configuration",{"name":19,"slug":20,"type":14},"2026-09-02T07:47:45.597063",{"slug":655,"name":655,"fn":656,"description":657,"org":658,"tags":659,"stars":24,"repoUrl":25,"updatedAt":666},"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},[660,661,664,665],{"name":11,"slug":8,"type":14},{"name":662,"slug":663,"type":14},"Deployment","deployment",{"name":22,"slug":23,"type":14},{"name":19,"slug":20,"type":14},"2026-09-02T07:46:51.573641",{"slug":668,"name":668,"fn":669,"description":670,"org":671,"tags":672,"stars":24,"repoUrl":25,"updatedAt":684},"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},[673,674,677,680,681],{"name":11,"slug":8,"type":14},{"name":675,"slug":676,"type":14},"Diagnostics","diagnostics",{"name":678,"slug":679,"type":14},"Operations","operations",{"name":19,"slug":20,"type":14},{"name":682,"slug":683,"type":14},"Triage","triage","2026-09-02T07:47:40.607437",{"slug":157,"name":157,"fn":686,"description":687,"org":688,"tags":689,"stars":24,"repoUrl":25,"updatedAt":694},"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},[690,691,692,693],{"name":11,"slug":8,"type":14},{"name":675,"slug":676,"type":14},{"name":678,"slug":679,"type":14},{"name":19,"slug":20,"type":14},"2026-09-02T07:48:04.154501",{"slug":4,"name":4,"fn":5,"description":6,"org":696,"tags":697,"stars":24,"repoUrl":25,"updatedAt":26},{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[698,699,700,701],{"name":16,"slug":17,"type":14},{"name":11,"slug":8,"type":14},{"name":22,"slug":23,"type":14},{"name":19,"slug":20,"type":14},{"slug":703,"name":703,"fn":704,"description":705,"org":706,"tags":707,"stars":24,"repoUrl":25,"updatedAt":711},"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},[708,709,710],{"name":11,"slug":8,"type":14},{"name":678,"slug":679,"type":14},{"name":19,"slug":20,"type":14},"2026-09-02T07:46:44.504107",{"slug":713,"name":713,"fn":714,"description":715,"org":716,"tags":717,"stars":24,"repoUrl":25,"updatedAt":724},"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},[718,719,720,721],{"name":11,"slug":8,"type":14},{"name":675,"slug":676,"type":14},{"name":19,"slug":20,"type":14},{"name":722,"slug":723,"type":14},"Storage","storage","2026-09-02T07:48:06.369058",18,{"items":727,"total":857},[728,747,764,770,777,785,792,799,805,812,825,845],{"slug":729,"name":729,"fn":730,"description":731,"org":732,"tags":733,"stars":744,"repoUrl":745,"updatedAt":746},"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},[734,735,738,741],{"name":11,"slug":8,"type":14},{"name":736,"slug":737,"type":14},"Compliance","compliance",{"name":739,"slug":740,"type":14},"Governance","governance",{"name":742,"slug":743,"type":14},"Policy","policy",1689,"https:\u002F\u002Fgithub.com\u002FAzure\u002Fazure-policy","2026-07-12T08:17:48.378432",{"slug":748,"name":748,"fn":749,"description":750,"org":751,"tags":752,"stars":761,"repoUrl":762,"updatedAt":763},"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},[753,754,755,758],{"name":11,"slug":8,"type":14},{"name":662,"slug":663,"type":14},{"name":756,"slug":757,"type":14},"Infrastructure as Code","infrastructure-as-code",{"name":759,"slug":760,"type":14},"Migration","migration",261,"https:\u002F\u002Fgithub.com\u002FAzure\u002Fazure-blueprints","2026-08-20T03:28:18.136156",{"slug":643,"name":643,"fn":644,"description":645,"org":765,"tags":766,"stars":24,"repoUrl":25,"updatedAt":653},{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[767,768,769],{"name":11,"slug":8,"type":14},{"name":650,"slug":651,"type":14},{"name":19,"slug":20,"type":14},{"slug":655,"name":655,"fn":656,"description":657,"org":771,"tags":772,"stars":24,"repoUrl":25,"updatedAt":666},{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[773,774,775,776],{"name":11,"slug":8,"type":14},{"name":662,"slug":663,"type":14},{"name":22,"slug":23,"type":14},{"name":19,"slug":20,"type":14},{"slug":668,"name":668,"fn":669,"description":670,"org":778,"tags":779,"stars":24,"repoUrl":25,"updatedAt":684},{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[780,781,782,783,784],{"name":11,"slug":8,"type":14},{"name":675,"slug":676,"type":14},{"name":678,"slug":679,"type":14},{"name":19,"slug":20,"type":14},{"name":682,"slug":683,"type":14},{"slug":157,"name":157,"fn":686,"description":687,"org":786,"tags":787,"stars":24,"repoUrl":25,"updatedAt":694},{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[788,789,790,791],{"name":11,"slug":8,"type":14},{"name":675,"slug":676,"type":14},{"name":678,"slug":679,"type":14},{"name":19,"slug":20,"type":14},{"slug":4,"name":4,"fn":5,"description":6,"org":793,"tags":794,"stars":24,"repoUrl":25,"updatedAt":26},{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[795,796,797,798],{"name":16,"slug":17,"type":14},{"name":11,"slug":8,"type":14},{"name":22,"slug":23,"type":14},{"name":19,"slug":20,"type":14},{"slug":703,"name":703,"fn":704,"description":705,"org":800,"tags":801,"stars":24,"repoUrl":25,"updatedAt":711},{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[802,803,804],{"name":11,"slug":8,"type":14},{"name":678,"slug":679,"type":14},{"name":19,"slug":20,"type":14},{"slug":713,"name":713,"fn":714,"description":715,"org":806,"tags":807,"stars":24,"repoUrl":25,"updatedAt":724},{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[808,809,810,811],{"name":11,"slug":8,"type":14},{"name":675,"slug":676,"type":14},{"name":19,"slug":20,"type":14},{"name":722,"slug":723,"type":14},{"slug":813,"name":813,"fn":814,"description":815,"org":816,"tags":817,"stars":24,"repoUrl":25,"updatedAt":824},"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},[818,819,820,823],{"name":16,"slug":17,"type":14},{"name":11,"slug":8,"type":14},{"name":821,"slug":822,"type":14},"Documentation","documentation",{"name":19,"slug":20,"type":14},"2026-09-02T07:46:52.116557",{"slug":826,"name":826,"fn":827,"description":828,"org":829,"tags":830,"stars":24,"repoUrl":25,"updatedAt":844},"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},[831,834,835,838,841],{"name":832,"slug":833,"type":14},"Automation","automation",{"name":11,"slug":8,"type":14},{"name":836,"slug":837,"type":14},"Azure DevOps","azure-devops",{"name":839,"slug":840,"type":14},"CI\u002FCD","ci-cd",{"name":842,"slug":843,"type":14},"GitHub Actions","github-actions","2026-09-02T07:48:08.951811",{"slug":639,"name":639,"fn":846,"description":847,"org":848,"tags":849,"stars":24,"repoUrl":25,"updatedAt":856},"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},[850,851,852,855],{"name":832,"slug":833,"type":14},{"name":11,"slug":8,"type":14},{"name":853,"slug":854,"type":14},"Quality Assurance","quality-assurance",{"name":19,"slug":20,"type":14},"2026-09-02T07:46:49.932123",145]