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
{{ message }}
This repository was archived by the owner on Dec 10, 2025. It is now read-only.
Logic Apps are maintained using JSON workflow definitions. In the traditional terraform hcl, you would set a workflow_definition field containing the JSON. This matches the design of the Azure portal, where the user can import/export a workflow definition JSON file.
The LogicAppWorkflow construct does not expose the workflowDefinition field. Currently it is possible to escape hatch out of cdktf by calling this.workflow.addOverride("workflow_definition", myJson);. However, this is a hack, and ideally the field would be exposed.
References
No response
Help Wanted
I'm interested in contributing a fix myself
Community Note
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Description
Logic Apps are maintained using JSON workflow definitions. In the traditional terraform hcl, you would set a
workflow_definitionfield containing the JSON. This matches the design of the Azure portal, where the user can import/export a workflow definition JSON file.The
LogicAppWorkflowconstruct does not expose theworkflowDefinitionfield. Currently it is possible to escape hatch out of cdktf by callingthis.workflow.addOverride("workflow_definition", myJson);. However, this is a hack, and ideally the field would be exposed.References
No response
Help Wanted
Community Note