Skip to content

Commit 59140ce

Browse files
committed
Review comments and Acrolinx
1 parent dd83daa commit 59140ce

File tree

4 files changed

+67
-318
lines changed

4 files changed

+67
-318
lines changed

articles/azure-functions/functions-how-to-azure-devops.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Continuously update function app code using Azure Pipelines
3-
description: Learn how to set up an Azure DevOps pipeline that targets Azure Functions.
3+
description: Learn how to use Azure Pipelines to set up a pipeline that builds and deploys apps to Azure Functions.
44
author: juliakm
55
ms.topic: conceptual
66
ms.date: 04/03/2024
@@ -47,7 +47,7 @@ Choose your task version at the top of the article. YAML pipelines aren't availa
4747

4848
---
4949

50-
Remember to upload the local code project to your GitHub or Azure Repos respository after you publish it to your function app.
50+
Remember to upload the local code project to your GitHub or Azure Repos repository after you publish it to your function app.
5151

5252
::: zone pivot="v1"
5353

@@ -56,8 +56,8 @@ Choose your task version at the top of the article. YAML pipelines aren't availa
5656
1. Sign in to your Azure DevOps organization and navigate to your project.
5757
1. In your project, navigate to the **Pipelines** page. Then select **New pipeline**.
5858
1. Select one of these options for **Where is your code?**:
59-
+ **GitHub**: You might be redirected to GitHub to sign in. If so, enter your GitHub credentials. When this is the first connection to GitHub, the wizard also walks you through the process of connecting DevOps to your GitHub accounts.
60-
+ **Azure Repos Git**: You are immediately able to choose a repository in your current DevOps project.
59+
+ **GitHub**: You might be redirected to GitHub to sign in. If so, enter your GitHub credentials. When this connection is your first GitHub connection, the wizard also walks you through the process of connecting DevOps to your GitHub accounts.
60+
+ **Azure Repos Git**: You're immediately able to choose a repository in your current DevOps project.
6161
1. When the list of repositories appears, select your sample app repository.
6262
1. Azure Pipelines analyzes your repository and in **Configure your pipeline** provides a list of potential templates. Choose the appropriate **function app** template for your language. If you don't see the correct template select **Show more**.
6363
1. Select **Save and run**, then select **Commit directly to the main branch**, and then choose **Save and run** again.
@@ -163,7 +163,7 @@ To learn about potential issues with these pipeline tasks, see [Functions not fo
163163
164164
#### [PowerShell](#tab/powershell)
165165
166-
You can use the following sample to create a YAML file to package a PowerShell app. PowerShell is supported only for Windows Azure Functions.
166+
You can use the following sample to create a YAML file to package a PowerShell app.
167167
168168
```yaml
169169
pool:
@@ -405,12 +405,12 @@ steps:
405405
artifactName: 'drop'
406406
```
407407

408-
Please check the generated archive to ensure that the deployed file has the right format.
408+
Check the generated archive to ensure that the deployed file has the right format.
409409
To learn about potential issues with these pipeline tasks, see [Functions not found after deployment](recover-python-functions.md#functions-not-found-after-deployment).
410410

411411
#### [PowerShell](#tab/powershell)
412412

413-
You can use the following sample to create a YAML file to package a PowerShell app. PowerShell is supported only for Windows Azure Functions.
413+
You can use the following sample to create a YAML file to package a PowerShell app.
414414

415415
```yaml
416416
pool:
@@ -431,7 +431,7 @@ steps:
431431

432432
## Deploy your app
433433

434-
You'll deploy with the [Azure Function App Deploy v2](/azure/devops/pipelines/tasks/reference/azure-function-app-v2) task. This task requires an [Azure service connection](/azure/devops/pipelines/library/service-endpoints) as an input. An Azure service connection stores the credentials to connect from Azure Pipelines to Azure.
434+
You'll deploy with the [Azure Function App Deploy v2](/azure/devops/pipelines/tasks/reference/azure-function-app-v2) task. This task requires an [Azure service connection](/azure/devops/pipelines/library/service-endpoints) as an input. An Azure service connection stores the credentials to connect from Azure Pipelines to Azure. You should create a connection that uses [workload identity federation](/azure/devops/pipelines/library/connect-to-azure#create-an-azure-resource-manager-service-connection-that-uses-workload-identity-federation).
435435

436436
The v2 version of the task includes support for newer applications stacks for .NET, Python, and Node. The task includes networking predeployment checks. When there are predeployment issues, deployment stops.
437437

articles/azure-functions/functions-how-to-custom-container.md

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Working with Azure Functions in containers
33
description: Learn how to work with function apps running in Linux containers.
4-
ms.date: 02/27/2024
4+
ms.date: 07/27/2024
55
ms.topic: how-to
66
ms.custom: build-2023, linux-related-content, build-2024
77
zone_pivot_groups: functions-container-hosting
@@ -116,7 +116,7 @@ Replace `<DOCKER_ID>` with your Docker Hub account ID.
116116

117117
---
118118

119-
At this point, you need to update an existing deployment to use the new image. You can updates the function app to use the new image either by using the Azure CLI or in the [Azure portal]:
119+
At this point, you need to update an existing deployment to use the new image. You can update the function app to use the new image either by using the Azure CLI or in the [Azure portal]:
120120

121121
### [Azure CLI](#tab/azure-cli2)
122122

@@ -147,7 +147,7 @@ The specified image version is deployed to your app.
147147
:::zone pivot="azure-functions"
148148
You should also consider [enabling continuous deployment](#enable-continuous-deployment-to-azure).
149149
::: zone-end
150-
:::zone pivot="azure-functions, container-apps"
150+
:::zone pivot="azure-functions"
151151
## Azure portal create using containers
152152

153153
When you create a function app in the [Azure portal], you can choose to deploy the function app from an image in a container registry. To learn how to create a containerized function app in a container registry, see [Create your function app in a container](#create-your-function-app-in-a-container).
@@ -185,12 +185,12 @@ The following steps create and deploy an existing containerized function app fro
185185

186186
1. After your function app resource is created, select **Go to resource** and in the function app page select **Deployment center**.
187187

188-
1. In the **Deployment center**, you can connect your container registry as the source of the image. You can also enable GitHub Actions or Azure Pipelines for more robust continuous deployment of updates to your container in the registry.
188+
1. In the **Deployment center**, you can connect your container registry as the source of the image. You can also enable GitHub Actions or Azure Pipelines for more robust continuous deployment of updates to your container in the registry.
189189
::: zone-end
190190
:::zone pivot="container-apps"
191191
## Azure portal create using containers
192192

193-
When you create a function app in the [Azure portal], you can choose to deploy the function app from an image in a container registry. To learn how to create a containerized function app in a container registry, see [Create your function app in a container](#create-your-function-app-in-a-container).
193+
When you create a Container Apps-hosted function app in the [Azure portal], you can choose to deploy your function app from an image in a container registry. To learn how to create a containerized function app in a container registry, see [Create your function app in a container](#create-your-function-app-in-a-container).
194194

195195
The following steps create and deploy an existing containerized function app from a container registry.
196196

@@ -211,13 +211,13 @@ The following steps create and deploy an existing containerized function app fro
211211

212212
<sup>*</sup>App name must be unique within the Azure Container Apps environment.
213213

214-
1. For **Azure Container Apps environment**, accept the suggested new environment in the **Consumption + Dedicated** plan. By default, the environment is created with the default workload profile and without zone redundancy, which minimizes costs. For more information, see [Azure Container Apps hosting of Azure Functions](functions-container-apps-hosting.md).
214+
1. Still on the **Basics** page, accept the suggested new environment for **Azure Container Apps environment**. To minimize costs, the new default environment is created in the **Consumption + Dedicated** with the default workload profile and without zone redundancy. For more information, see [Azure Container Apps hosting of Azure Functions](functions-container-apps-hosting.md).
215215

216216
You can also choose to use an existing Container Apps environment. To create a custom environment, instead select **Create new**. In the **Create Container Apps Environment** page, you can add nondefault workload profiles or enable zone redundancy. To learn about environments, see [Azure Container Apps environments](../container-apps/environment.md).
217217

218218
1. Select the **Deployment** tab and unselect **Use quickstart image**. Otherwise, the function app is deployed from the base image for your function app language.
219219

220-
1. Choose your **Image type**, public or private. Choose **Private** if you're using Azure Container Registry or some other private registry. Supply the **Image** name, including the registry prefix. If you're using a private registry, provide the image registry authentication credentials.
220+
1. Choose your **Image type**, public or private. Choose **Private** if you're using Azure Container Registry or some other private registry. Supply the **Image** name, including the registry prefix. If you're using a private registry, provide the image registry authentication credentials. The **Public** setting only supports images stored publicly in Docker Hub.
221221

222222
1. Under **Container resource allocation**, select your desired number of CPU cores and available memory. If your environment has other workload profiles added, you can select a nondefault **Workload profile**. Choices on this page affect the cost of hosting your app. See the [Container Apps pricing page](https://azure.microsoft.com/pricing/details/container-apps/) to estimate your potential costs.
223223

@@ -255,7 +255,7 @@ Based on your changes, a new image is deployed to your app or new allocations ar
255255

256256
1. To make updates, modify any of the image settings, such as the **Full Image Name and Tag** and then select **Save**.
257257

258-
The a new image is deployed to your app based on your new settings.
258+
The new image is deployed to your app based on your new settings.
259259
::: zone-end
260260

261261
---
@@ -275,7 +275,7 @@ You enable workload profiles when you create your container app environment. For
275275

276276
You can add, edit, and delete profiles in your environment. For an example, see [Add profiles](../container-apps/workload-profiles-manage-cli.md#add-profiles).
277277

278-
When you create a containerized function app in an environment that has workload profiles enabled, you should also specify the profile in which to run. You do this by using the `--workload-profile-name` parameter of the [`az functionapp create`](/cli/azure/functionapp#az-functionapp-create) command, like in this example:
278+
When you create a containerized function app in an environment that has workload profiles enabled, you should also specify the profile in which to run. You specify the profile by using the `--workload-profile-name` parameter of the [`az functionapp create`](/cli/azure/functionapp#az-functionapp-create) command, like in this example:
279279

280280
```azurecli
281281
az functionapp create --name <APP_NAME> --storage-account <STORAGE_NAME> --environment MyContainerappEnvironment --resource-group AzureFunctionsContainers-rg --functions-version 4 --runtime <LANGUAGE_STACK> --image <IMAGE_URI> --workload-profile-name <PROFILE_NAME> --cpu <CPU_COUNT> --memory <MEMORY_SIZE>
@@ -309,7 +309,7 @@ Azure Functions lets you work with application settings for containerized functi
309309
:::zone pivot="container-apps"
310310
## Enable continuous deployment to Azure
311311

312-
When you host your containerized function app on Azure Container Apps, there are two ways to set up continous deployment from a source code repository:
312+
When you host your containerized function app on Azure Container Apps, there are two ways to set up continuous deployment from a source code repository:
313313

314314
+ [Azure Pipelines](./functions-how-to-azure-devops.md#deploy-a-container)
315315
+ [GitHub Actions](./functions-how-to-github-actions.md?tabs=container)

0 commit comments

Comments
 (0)