docs: the Standard workflow.json shape and its three real differences - #43
Merged
Conversation
The Logic App standard documented Consumption whole-definition authoring
and the Standard app HOST, but never the Standard workflow ARTEFACT. So
it never said that a Standard workflow is a file rather than an ARM
resource, never showed the {definition, kind} wrapper, and never
mentioned the connections.json authentication format.
Adds all three, plus the point that matters most for reuse: the
definition block inside a Standard workflow.json is identical to a
Consumption definition, so every WDL rule in the document applies
unchanged and the annotated schema validates both.
Also records the failure that produces an unhelpful error: Visual Studio
Code writes managed API connections with a Raw scheme and an appsetting
key, Azure expects ManagedServiceIdentity, and shipping the local shape
unchanged is the most common Standard deployment failure.
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Logic App standard documented Consumption whole-definition authoring and the Standard app host, but never the Standard workflow artefact.
So it never said that on Standard a workflow is a file rather than an ARM resource, never showed the
{definition, kind}wrapper, and never mentioned theconnections.jsonauthentication format.What is added
connections.jsonandhost.json.workflow.jsonwrapper, with the point that matters most for reuse: thedefinitionblock is identical to a Consumption definition, so every WDL rule in the document applies unchanged and the annotated schema validates both.kindisStatefulunless you have measured that 5 minutes is enough, cross-referenced to the hosting model section.@appsetting()rather than the ARM body, and connections are V2 requiring access policies rather than V1 rejecting them.connections.jsontrap. VS Code writes managed API connections with aRawscheme and an appsetting key; Azure expectsManagedServiceIdentity. Shipping the local shape unchanged is the most common Standard deployment failure and the error does not say so.Why in the doc rather than the agent
azure-logic-app-standards.txtis a knowledge pack forlogic-app-author, so documenting this here teaches the agent for free at the nextjust update-knowledge. The agent has 73 characters of headroom against its warning line, so this could not have gone into its instructions, and it should not have: theworkflow.jsonshape is a fact, and facts belong in knowledge.Verification
No broken anchors in the built output, the new section id resolves,
npm run buildclean, no em or en dashes.