azurermLogicAppTriggerCustom
Manages a Custom Trigger within a Logic App Workflow
Example Usage
/*Provider bindings are generated by running cdktf get.
See https://cdk.tf/provider-generation for more details.*/
import * as azurerm from "./.gen/providers/azurerm";
/*The following providers are missing schema information and might need manual adjustments to synthesize correctly: azurerm.
For a more precise conversion please use the --provider flag in convert.*/
const azurermResourceGroupExample = new azurerm.resourceGroup.ResourceGroup(
this,
"example",
{
location: "West Europe",
name: "workflow-resources",
}
);
const azurermLogicAppWorkflowExample =
new azurerm.logicAppWorkflow.LogicAppWorkflow(this, "example_1", {
location: azurermResourceGroupExample.location,
name: "workflow1",
resource_group_name: azurermResourceGroupExample.name,
});
/*This allows the Terraform resource name to match the original name. You can remove the call if you don't need them to match.*/
azurermLogicAppWorkflowExample.overrideLogicalId("example");
const azurermLogicAppTriggerCustomExample =
new azurerm.logicAppTriggerCustom.LogicAppTriggerCustom(this, "example_2", {
body: '{\n "recurrence": {\n "frequency": "Day",\n "interval": 1\n },\n "type": "Recurrence"\n}\n',
logic_app_id: azurermLogicAppWorkflowExample.id,
name: "example-trigger",
});
/*This allows the Terraform resource name to match the original name. You can remove the call if you don't need them to match.*/
azurermLogicAppTriggerCustomExample.overrideLogicalId("example");
Argument Reference
The following arguments are supported:
name
- (Required) Specifies the name of the HTTP Trigger to be created within the Logic App Workflow. Changing this forces a new resource to be created.
-> NOTE: This name must be unique across all Triggers within the Logic App Workflow.
-
logicAppId
- (Required) Specifies the ID of the Logic App Workflow. Changing this forces a new resource to be created. -
body
- (Required) Specifies the JSON Blob defining the Body of this Custom Trigger.
-> NOTE: To make the Trigger more readable, you may wish to consider using HEREDOC syntax (as shown above) or the localFile
resource to load the schema from a file on disk.
Attributes Reference
The following attributes are exported:
id
- The ID of the Trigger within the Logic App Workflow.
Timeouts
The timeouts
block allows you to specify timeouts for certain actions:
create
- (Defaults to 30 minutes) Used when creating the Logic App Custom Trigger.update
- (Defaults to 30 minutes) Used when updating the Logic App Custom Trigger.read
- (Defaults to 5 minutes) Used when retrieving the Logic App Custom Trigger.delete
- (Defaults to 30 minutes) Used when deleting the Logic App Custom Trigger.
Import
Logic App Custom Triggers can be imported using the resourceId
, e.g.
terraform import azurerm_logic_app_trigger_custom.custom1 /subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/mygroup1/providers/Microsoft.Logic/workflows/workflow1/triggers/custom1
-> NOTE: This ID is unique to Terraform and doesn't directly match to any other resource. To compose this ID, you can take the ID Logic App Workflow and append /triggers/{nameOfTheTrigger}
.