docs: make the whole-definition azapi path the Logic App standard

[craigthackerx]

The Terraform section of the Logic App standard documented only the per-resource azurerm path: the azurerm shell module plus azurerm_logic_app_trigger_* and azurerm_logic_app_action_* resources, roughly 700 lines of it. terraform-azapi-logic-app-workflow was not mentioned anywhere, and templatefile appeared three times, all in passing on the azurerm path.

What changes

New: the authoring model is now the first decision in the Terraform section, with a comparison table and the whole-definition path named as the standard. The reasoning is that Logic Apps are authored in a designer, and the per-resource split discards the artefact that designer produces, creates a second ordering graph that can disagree with runAfter, and exposes the CannotDisableTriggerConcurrency trap that only fires when a trigger is PATCHed individually out of a live definition.

New: ### Whole-definition workflows with azapi, covering

• the designer → code view → templates/<name>.json.tftpl → ctrl+F → plan round trip
• the three wrapper shapes that paste in unchanged, and why the unwrap is unambiguous
• the token contract: what to tokenise, what not to, and the rule to prefer a typed workflow parameter over a token for anything an operator might want to see or change
• that WDL's @{} does not collide with Terraform's ${}, plus the $${ and %%{ escapes for the two characters that do
• the module call, and that templatefile(...) goes straight into definition with no jsonencode/jsondecode wrapper, unlike the per-resource path
• declarations in the definition versus values in Terraform, and the 4.4.0 precedence order
• V1-only connections on Consumption and the two halves of managed identity auth
• deploy_tier for sibling dispatch ordering
• sensitive_body for secure values and the trimmed response_export_values default
• the validation versus check split, as a table

Reframed, not removed: the per-resource sections stay, since the azurerm module is published and real estates use it, but they now carry lead-ins saying they are the alternative path.

One thing you need to know

libre-devops/logic-app-workflow/azapi does not resolve on the Terraform Registry. I paginated all 136 modules in the namespace; the azapi Logic App module is not among them, though api-connection/azapi, summary-rules/azapi and others are. The module is released on GitHub at 4.4.0 (2026-07-30) and its own README already uses the registry address.

The doc therefore shows the registry form as the standard, with a callout giving the git tag source as the interim. Publish the module and that callout should be deleted.

Verification

• Module interface read from variables.tf, HEADER.md and both examples in the repo, not from memory.
• Registry absence confirmed by paginating the full namespace.
• No broken internal anchors in the built output; the four cross-references resolve.
• npm run build clean. No em dashes or en dashes.

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None