Skip to content

Commit dbe0b16

Browse files
committed
Apply feedback from review with Mukta
1 parent 416157c commit dbe0b16

File tree

5 files changed

+28
-37
lines changed

5 files changed

+28
-37
lines changed

articles/azure-app-configuration/TOC.yml

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -21,14 +21,14 @@
2121
href: quickstart-dotnet-app.md
2222
- name: Azure Functions in .NET Core
2323
href: quickstart-azure-functions-csharp.md
24-
- name: Container Apps
25-
href: quickstart-container-apps.md
2624
- name: Java Spring
2725
href: quickstart-java-spring-app.md
28-
- name: JavaScript/Node.js
29-
href: quickstart-javascript.md
3026
- name: Python
3127
href: quickstart-python-provider.md
28+
- name: JavaScript/Node.js
29+
href: quickstart-javascript.md
30+
- name: Azure Container Apps
31+
href: quickstart-container-apps.md
3232
- name: Feature management
3333
items:
3434
- name: ASP.NET Core

articles/azure-app-configuration/index.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -80,7 +80,7 @@ landingContent:
8080
url: quickstart-python.md
8181
- text: Azure Resource Manager template
8282
url: quickstart-resource-manager.md
83-
- text: Container Apps
83+
- text: Azure Container Apps
8484
url: quickstart-container-apps.md
8585
- linkListType: tutorial
8686
links:
28.3 KB
Loading
147 KB
Loading

articles/azure-app-configuration/quickstart-container-apps.md

Lines changed: 23 additions & 32 deletions
Original file line numberDiff line numberDiff line change
@@ -12,44 +12,31 @@ ms.author: malev
1212

1313
# Quickstart: Use Azure App Configuration in Azure Container Apps
1414

15-
In this quickstart, you will use Azure App Configuration in an ASP.NET Core app running in Azure Container Apps. This way, you can centralize the storage and management of your Container Apps configuration. This quickstart leverages the ASP.NET Core app created in [Quickstart: Create an ASP.NET Core app with App Configuration](./quickstart-aspnet-core-app.md). You will containerize the app and deploy it to Azure Container Apps. Complete the quickstart before you continue.
15+
In this quickstart, you will use Azure App Configuration in an app running in Azure Container Apps. This way, you can centralize the storage and management of the configuration of your apps in Container Apps. This quickstart leverages the ASP.NET Core app created in [Quickstart: Create an ASP.NET Core app with App Configuration](./quickstart-aspnet-core-app.md). You will containerize the app and deploy it to Azure Container Apps. Complete the quickstart before you continue.
1616

1717
> [!TIP]
1818
> While following this quickstart, preferably register all new resources within a single resource group, so that you can regroup them all in a single place and delete them faster later on if you don't need them anymore.
1919
2020
## Prerequisites
2121

22-
- The App Configuration store and the ASP.NET Core App that you created in the [Quickstart: Create an ASP.NET Core app with App Configuration](./quickstart-aspnet-core-app.md).
22+
- An application using an App Configuration store. If you don't have one, create an instance using the [Quickstart: Create an ASP.NET Core app with App Configuration](./quickstart-aspnet-core-app.md).
2323
- [Docker Desktop](https://www.docker.com/products/docker-desktop)
2424
- The [Azure CLI](/cli/azure/install-azure-cli)
25-
26-
## Create an Azure Container Apps instance
27-
28-
Start by creating a basic [Azure Container Apps](../container-apps/overview.md) instance and a Container Apps environment, where you'll later host your app.
29-
30-
This Azure service is designed to run containerized applications.
31-
32-
#### [Portal](#tab/azure-portal)
33-
34-
To create the container app and container apps environment using the Azure portal, follow the [Azure Container Apps quickstart](/azure/container-apps/quickstart-portal).
35-
36-
#### [Azure CLI](#tab/azure-cli)
37-
38-
To create the container app and container apps environment using the Azure CLI, follow the [Azure Container Apps quickstart](/azure/container-apps/get-started). The created container app contains a default image.
25+
- An Azure Container Apps instance. If you don't have one, create an instance using the [Azure portal](/azure/container-apps/quickstart-portal) or [the CLI](/azure/container-apps/get-started).
3926

4027
---
4128

42-
## Connect Azure Container Apps to Azure App Configuration
29+
## Connect the container app to Azure App Configuration
4330

44-
In the next step, you'll add the connection string of your App Configuration store to the secret of your Container App and add an environment variable to your container to reference the secret. You use the [Service Connector](../service-connector/overview.md) to do this in a few steps without managing the connection information yourself.
31+
The first step of this guide is to connect your container app to your configuration store. To do this, add the connection string of your App Configuration store to the secret of your Container App, and add an environment variable to your container to reference the secret. Use [Service Connector](../service-connector/overview.md) to do this in a few steps without managing the connection information yourself.
4532

4633
In the Azure portal, connect the container app to Azure App Configuration following the [Service Connector quickstart for Azure Container Apps](../service-connector/quickstart-portal-container-apps.md). While following the steps of the quickstart:
4734

4835
- In the **Basics** tab:
49-
5036
- select **App Configuration** for **Service type**
51-
- pick the App Configuration store created in the quickstart for "**App Configuration**"
52-
- select **.NET** for **Client Type**.
37+
- pick your App Configuration store for "**App Configuration**"
38+
39+
:::image type="content" border="true" source="media\connect-container-app\use-service-connector.png" alt-text="Screenshot the Azure platform showing a form in the Service Connector menu in a Container App.":::
5340

5441
- In the **Authentication** tab:
5542
- pick **Connection string** authentication type and **Read-Only** for "**Permissions for the connection string**
@@ -58,7 +45,7 @@ In the Azure portal, connect the container app to Azure App Configuration follow
5845

5946
Once done, an environment variable named **ConnectionStrings__AppConfig** will be added to the container of your Container App. Its value is a reference of the Container App secret, the connection string of your App Configuration store. The _ConnectionStrings__AppConfig_ is the environment variable your app built from the quickstart will look for.
6047

61-
## Build the container
48+
## Build a container
6249

6350
1. Run the [dotnet publish](/dotnet/core/tools/dotnet-publish) command to build the app in release mode and create the assets in the *published* folder.
6451

@@ -90,7 +77,7 @@ Create an Azure Container Registry (ACR). ACR enables you to build, store, and m
9077
1. To create the container registry, follow the [Azure Container Registry quickstart](/azure/container-registry/container-registry-get-started-portal).
9178
1. Once the deployment is complete, open your ACR instance and from the left menu, select **Settings > Access keys**.
9279
1. Take note of the **Login server** value listed on this page. You'll use this information in a later step.
93-
1. Switch **Admin user** to *Enabled*. This option lets you connect the ACR to Azure Container Apps using admin user credentials.
80+
1. Switch **Admin user** to *Enabled*. This option lets you connect the ACR to Azure Container Apps using admin user credentials. If you leave it disabled, you can still connect the container registry and the container app using a managed identity.
9481
9582
#### [Azure CLI](#tab/azure-cli)
9683
@@ -112,14 +99,14 @@ Push the Docker image to the ACR created earlier.
11299
113100
The command returns `Login Succeeded` once login is successful.
114101
115-
1. Use [docker tag](https://docs.docker.com/engine/reference/commandline/tag/) to tag the image with the ACR name
102+
1. Use [docker tag](https://docs.docker.com/engine/reference/commandline/tag/) to tag the image appropriate details.
116103
117104
```docker
118105
docker tag aspnetapp myregistry.azurecr.io/aspnetapp:v1
119106
```
120107
121108
> [!TIP]
122-
> To review the list of your existing docker images and tags, run `docker image ls`.
109+
> To review the list of your existing docker images and tags, run `docker image ls`. In this scenario, you should see at least two images: `aspnetapp` and `myregistry.azurecr.io/aspnetapp`.
123110
124111
1. Use [docker push](https://docs.docker.com/engine/reference/commandline/push/) to push the image to the container registry. This example creates the *aspnetapp* repository in ACR containing the `aspnetapp` image. In the example below, replace the placeholders `<login-server`, `<image-name>` and `<tag>` by the ACR's log-in server value, the image name and the image tag.
125112
@@ -135,6 +122,10 @@ Push the Docker image to the ACR created earlier.
135122
docker push myregistry.azurecr.io/aspnetapp:v1
136123
```
137124
125+
1. Open your Azure Container Registry in the Azure portal and confirm that under **Repositories**, you can see your new repository.
126+
127+
:::image type="content" border="true" source="media\connect-container-app\container-registry-repository.png" alt-text="Screenshot of the Azure platform showing a repository in Azure Container Registries.":::
128+
138129
## Add your container image to Azure Container Apps
139130
140131
Update the existing container app by importing the docker image you created and pushed to ACR earlier.
@@ -147,13 +138,13 @@ Update the existing container app by importing the docker image you created and
147138
1. Under **Container image**, click on the name of the existing container image.
148139
1. Update the following settings:
149140
150-
| Setting | Suggested value | Description |
151-
|-----------------------|---------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
152-
| Image source | *Azure Container Registry* | Select Azure Container Registry as your image source. |
153-
| Authentication | *Admin Credentials* | Connect with the admin user credentials enabled in the Azure Container Registry. |
154-
| Registry | *myregistry.azurecr.io* | Select the Azure Container Registry you created earlier. |
155-
| Image | *aspnetapp* | Select the docker image you created and pushed to ACR earlier. |
156-
| Image tag | *v1* | Select your image tag from the list. |
141+
| Setting | Suggested value | Description |
142+
|----------------|----------------------------|----------------------------------------------------------------------------------|
143+
| Image source | *Azure Container Registry* | Select Azure Container Registry as your image source. |
144+
| Authentication | *Admin Credentials* | Use the admin user credential option that was enabled earlier in the container registry. You can also [use a managed identity](../container-apps/managed-identity-image-pull.md?tabs=azure-cli&pivots=azure-portal), in which case you will need to manually enter the image and tag in the form. |
145+
| Registry | *myregistry.azurecr.io* | Select the Azure Container Registry you created earlier. |
146+
| Image | *aspnetapp* | Select the docker image you created and pushed to ACR earlier. |
147+
| Image tag | *v1* | Select your image tag from the list. |
157148
158149
1. Select **Save** and then **Create** to deploy the update to Azure Container App.
159150

0 commit comments

Comments
 (0)