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
description: Automate tasks and workflows that create and manage container deployments in Azure Container Instances by using Azure Logic Apps
4
4
services: logic-apps, container-instances
5
5
ms.service: logic-apps
6
6
ms.suite: integration
7
7
author: dlepow
8
8
ms.author: danlep
9
9
ms.manager: gwallace
10
-
ms.reviewer:
11
-
ms.assetid:
10
+
ms.reviewer: estfan, macolso
12
11
ms.topic: article
13
12
tags: connectors
14
13
ms.date: 11/11/2019
15
14
---
16
15
17
-
# Trigger and manage Azure Container Instances deployments by using Azure Logic Apps
16
+
# Deploy and manage Azure Container Instances by using Azure Logic Apps
18
17
19
18
With Azure Logic Apps and the Azure Container Instance connector,
20
-
you can set up automated tasks and workflows that trigger and manage deployments of [container groups](../container-instances/container-instances-container-groups.md). The connector supports the following Azure Container Instances actions:
19
+
you can set up automated tasks and workflows that deploy and manage [container groups](../container-instances/container-instances-container-groups.md). The Container Instance connector supports the following actions:
21
20
22
21
* Create or delete a container group
23
22
* Get the properties of a container group
24
23
* Get a list of container groups
25
24
* Get the logs of a container instance
26
25
27
-
Use these actions in your logic apps to perform an action such as running a container workload in response to a Logic Apps trigger. You can also have other actions use the output from Azure Container Instances actions.
26
+
Use these actions in your logic apps for tasks such as running a container workload in response to a Logic Apps trigger. You can also have other actions use the output from Container Instance actions.
28
27
29
28
This connector provides only actions, so to start your logic app,
30
29
use a separate trigger, such as a **Recurrence** trigger to run a container workload on a regular schedule. Or, you might have need to trigger a container group deployment after an event such as arrival of an Outlook e-mail.
@@ -44,7 +43,7 @@ If you're new to logic apps, review
44
43
To use an action, start your logic app with another trigger,
45
44
for example, the **Recurrence** trigger.
46
45
47
-
## Trigger an Azure Container Instance action
46
+
## Add a Container Instance action
48
47
49
48
[!INCLUDE [Create connection general intro](../../includes/connectors-create-connection-general-intro.md)]
50
49
@@ -75,18 +74,11 @@ and continue building your logic app's workflow.
For an explanation of the properties you can set in the **Create container group** action, see the [connector reference](/connectors/aci/) or container group [YAML reference](../container-instances/container-instances-reference-yaml.md).
79
-
80
77
## Connector reference
81
78
82
79
For technical details about triggers, actions, and limits, which are
83
80
described by the connector's OpenAPI (formerly Swagger) description,
84
-
review the connector's [reference page](/connectors/aci/).
85
-
86
-
## Get support
87
-
88
-
* For questions, visit the [Azure Logic Apps forum](https://social.msdn.microsoft.com/Forums/en-US/home?forum=azurelogicapps).
89
-
* To submit or vote on feature ideas, visit the [Logic Apps user feedback site](https://aka.ms/logicapps-wish).
81
+
review the connector's [reference page](/connectors/aci/) or container group [YAML reference](../container-instances/container-instances-reference-yaml.md).
0 commit comments