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
Copy file name to clipboardExpand all lines: articles/service-connector/how-to-build-connections-with-iac-tools.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,16 +17,16 @@ Service Connector helps users connect their compute services to target backing s
17
17
18
18
## Solution overview
19
19
20
-
Translating the infrastructure to IaC templates usually involves two major parts: the logics to provision source and target services, and the logics to build connections. To implement the logics to provision source and target services, there are two options:
20
+
Translating the infrastructure to IaC templates usually involves two major parts: the logic to provision source and target services, and the logic to build connections. To implement the logic to provision source and target services, there are two options:
21
21
22
22
* Authoring the template from scratch
23
23
* Exporting the template from Azure and polish it
24
24
25
-
To implement the logics to build connections, there are three options:
25
+
To implement the logic to build connections, there are three options:
26
26
27
27
* Using Service Connector and store configuration in App Configuration
28
28
* Using Service Connector in the template
29
-
* Using template logics to configure source and target services directly
29
+
* Using template logic to configure source and target services directly
30
30
31
31
Combinations of these different options can produce different solutions. Due to [IaC limitations](./known-limitations.md) in Service Connector, we recommend that you implement the following solutions in the order presented below. To apply these solutions, you must understand the IaC tools and the template authoring grammar.
32
32
@@ -41,7 +41,7 @@ Combinations of these different options can produce different solutions. Due to
41
41
42
42
## Authoring templates
43
43
44
-
The following sections show how to create a web app and a storage account and connect them with a system-assigned identity using Bicep. It shows how to do this both using Service Connector and using template logics.
44
+
The following sections show how to create a web app and a storage account and connect them with a system-assigned identity using Bicep. It shows how to do this both using Service Connector and using template logic.
45
45
46
46
### Provision source and target services
47
47
@@ -116,7 +116,7 @@ If the resources you're provisioning are exactly the same ones as the ones you h
116
116
117
117
:::image type="content" source="./media/how-to/export-webapp-template.png" alt-text="Screenshot of the Azure portal, exporting arm template of a web app.":::
118
118
119
-
### Build connection logics
119
+
### Build connection logic
120
120
121
121
### Using Service Connector and storing configuration in App Configuration
Creating connections between the source and target service using Service Connector is the preferred and recommended way if the [Service Connector ](./known-limitations.md)[IaC limitation](./known-limitations.md) doesn't matter for your scenario. Service Connector makes the template simpler and also provides additional elements, such as the connection health validation, which you won't have if you're building connections through template logics directly.
163
+
Creating connections between the source and target service using Service Connector is the preferred and recommended way if the [Service Connector ](./known-limitations.md)[IaC limitation](./known-limitations.md) doesn't matter for your scenario. Service Connector makes the template simpler and also provides additional elements, such as the connection health validation, which you won't have if you're building connections through template logic directly.
164
164
165
165
```bicep
166
166
// The template builds a connection between a webapp and a storage account
@@ -202,9 +202,9 @@ For the formats of properties and values needed when creating a Service Connecto
202
202
203
203
:::image type="content" source="./media/how-to/export-sc-template.png" alt-text="Screenshot of the Azure portal, exporting arm template of a service connector resource.":::
204
204
205
-
**Using template logics**
205
+
**Using template logic**
206
206
207
-
For the scenarios where the Service Connector [IaC limitation](./known-limitations.md) matters, consider building connections using the template logics directly. The following template is an example showing how to connect a storage account to a web app using a system-assigned identity.
207
+
For the scenarios where the Service Connector [IaC limitation](./known-limitations.md) matters, consider building connections using the template logic directly. The following template is an example showing how to connect a storage account to a web app using a system-assigned identity.
208
208
209
209
```bicep
210
210
// The template builds a connection between a webapp and a storage account
When building connections using template logics directly, it's crucial to understand what Service Connector does for each kind of authentication type, as the template logics are equivalent to the Service Connector backend operations. The following table shows the operation details that you need translate to template logics for each kind of authentication type.
253
+
When building connections using template logic directly, it's crucial to understand what Service Connector does for each kind of authentication type, as the template logic are equivalent to the Service Connector backend operations. The following table shows the operation details that you need translate to template logic for each kind of authentication type.
0 commit comments