Azure Logic App Integration Account Batch Configuration
This page shows how to write Terraform and Azure Resource Manager for Logic App Integration Account Batch Configuration and write them securely.
azurerm_logic_app_integration_account_batch_configuration (Terraform)
The Integration Account Batch Configuration in Logic App can be configured in Terraform with the resource name azurerm_logic_app_integration_account_batch_configuration
. The following sections describe how to use the resource and its parameters.
Example Usage from GitHub
An example could not be found in GitHub.
Parameters
The following arguments are supported:
name
- (Required) The name which should be used for this Logic App Integration Account Batch Configuration. Changing this forces a new resource to be created.resource_group_name
- (Required) The name of the Resource Group where the Logic App Integration Account Batch Configuration should exist. Changing this forces a new resource to be created.integration_account_name
- (Required) The name of the Logic App Integration Account. Changing this forces a new resource to be created.batch_group_name
- (Required) The batch group name of the Logic App Integration Batch Configuration. Changing this forces a new resource to be created.release_criteria
- (Required) Arelease_criteria
block as documented below, which is used to select the criteria to meet before processing each batch.metadata
- (Optional) A JSON mapping of any Metadata for this Logic App Integration Account Batch Configuration.
A release_criteria
block exports the following:
batch_size
- (Optional) The batch size in bytes for the Logic App Integration Batch Configuration.message_count
- (Optional) The message count for the Logic App Integration Batch Configuration.recurrence
- (Optional) Arecurrence
block as documented below.
A recurrence
block exports the following:
frequency
- (Required) The frequency of the schedule. Possible values areDay
,Hour
,Minute
,Month
,Second
,Week
andYear
.interval
- (Required) The number offrequency
s between runs.end_time
- (Optional) The end time of the schedule, formatted as an RFC3339 string.schedule
- (Optional) Aschedule
block as documented below.start_time
- (Optional) The start time of the schedule, formatted as an RFC3339 string.time_zone
- (Optional) The timezone of the start/end time.
A schedule
block exports the following:
hours
- (Optional) A list containing a single item, which specifies the Hour interval at which this recurrence should be triggered.minutes
- (Optional) A list containing a single item which specifies the Minute interval at which this recurrence should be triggered.month_days
- (Optional) A list of days of the month that the job should execute on.monthly
- (Optional) Amonthly
block as documented below.week_days
- (Optional) A list of days of the week that the job should execute on. Possible values areSunday
,Monday
,Tuesday
,Wednesday
,Thursday
,Friday
andSaturday
.
A monthly
block exports the following:
weekday
- (Required) The day of the occurrence. Possible values areSunday
,Monday
,Tuesday
,Wednesday
,Thursday
,Friday
andSaturday
.week
- (Required) The occurrence of the week within the month.
In addition to the Arguments listed above - the following Attributes are exported:
id
- The ID of the Logic App Integration Account Batch Configuration.
Explanation in Terraform Registry
Manages a Logic App Integration Account Batch Configuration.
Microsoft.Logic/integrationAccounts/batchConfigurations (Azure Resource Manager)
The integrationAccounts/batchConfigurations in Microsoft.Logic can be configured in Azure Resource Manager with the resource name Microsoft.Logic/integrationAccounts/batchConfigurations
. The following sections describe how to use the resource and its parameters.
Example Usage from GitHub
An example could not be found in GitHub.