» azurerm_logic_app_trigger_custom

Manages a Custom Trigger within a Logic App Workflow

» Example Usage

resource "azurerm_resource_group" "test" {
  name     = "workflow-resources"
  location = "East US"
}

resource "azurerm_logic_app_workflow" "test" {
  name                = "workflow1"
  location            = "${azurerm_resource_group.test.location}"
  resource_group_name = "${azurerm_resource_group.test.name}"
}

resource "azurerm_logic_app_trigger_custom" "test" {
  name         = "example-trigger"
  logic_app_id = "${azurerm_logic_app_workflow.test.id}"

  body = <<BODY
{
  "recurrence": {
    "frequency": "Day",
    "interval": 1
  },
  "type": "Recurrence"
}
BODY
}

» 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.

logic_app_id - (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 local_file 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.

» Import

Logic App Custom Triggers can be imported using the resource id, 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/{name of the trigger}.