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: docs/continuous-delivery/deploy-srv-diff-platforms/azure/azure-function-tutorial.md
+18-4Lines changed: 18 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -111,9 +111,9 @@ Within the same resource group, you can't mix Windows and Linux apps in the same
111
111
:::info note
112
112
In the deploy steps under Container Configuration, specify the appropriate image based on your container registry:
113
113
114
-
1.[ECR Image for azure function plugin](https://gallery.ecr.aws/harness/harness/azure-function-plugin)
115
-
2.[Docker Image for azure function plugin](https://hubgw.docker.com/r/harnessdev/azure-function-plugin)
116
-
3. GAR Images for azure function plugin:
114
+
1.[Docker Image for Azure Function Plugin](https://hub.docker.com/r/harness/azure-function-plugin/tags)
115
+
2.[ECR Image for Azure Function Plugin](https://gallery.ecr.aws/harness/harness/azure-function-plugin)
116
+
3. GAR Images for Azure Function Plugin:
117
117
- Europe region: [GAR Image Repository for Azure Function Plugin (Europe)](https://console.cloud.google.com/artifacts/docker/gar-prod-setup/europe/harness-public/harness%2Fazure-function-plugin?inv=1&invt=Ab5cNA)
118
118
119
119
:::
@@ -124,10 +124,24 @@ In the execution tab of the pipeline stage, select **Add Step** and select **Azu
124
124
125
125
Currently Azure function deployment supports basic and custom deployment strategy.
126
126
127
+
:::important Container Execution Requirements
128
+
The Azure Function Deploy step requires a containerized execution environment:
129
+
130
+
- If you select the **Basic** deployment strategy, Harness automatically adds a container Step Group with the Azure Function Deploy step inside it.
131
+
132
+
- If you select the **Custom** deployment strategy, you need to manually:
133
+
1. Add a Step Group to your pipeline
134
+
2. Enable the **Container** option in the Step Group
135
+
3. Configure the Step Group to use your Kubernetes connector
136
+
4. Add the Azure function Deploy step inside this Step Group
137
+
138
+
Failure to run the step in a containerized execution context will likely result in deployment failures.
139
+
:::
140
+
127
141
The Azure function Deploy step has the following settings:
128
142
129
143
***Name:** Enter a name for the step.
130
-
***Timeout:**Enter a minimum of**10m**. The slot deployment relies on Azure and can take time.
144
+
***Timeout:**Enter a minimum of**10m**. The slot deployment relies on Azure and can take time.
131
145
***Container Registry**: Specify the connector that connects to the azure infrastructure and container registry you wish to use.
132
146
***Image**: Specify the artifact image you want to run.
133
147
***Function app**: Specify the Azure Container to be used.
0 commit comments