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
Fix build warnings in functions-secrets-tutorial.md
- Change nested tab IDs from parent+child syntax (#tab/in-place+portal,
#tab/keyvault+portal, etc.) to simple #tab/portal and #tab/cli to
eliminate duplicate tab ID and different tab ID set warnings
- Rename duplicate H2 headings: 'Verify the secret' becomes
'Verify the Container Apps secret' and 'Verify the Key Vault secret'
Co-authored-by: Copilot <[email protected]>
Copy file name to clipboardExpand all lines: articles/container-apps/functions-secrets-tutorial.md
+15-15Lines changed: 15 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,7 +44,7 @@ Azure Container Apps provides two ways to store secrets that your function code
44
44
45
45
Container Apps stores secrets in the app's `configuration.secrets` array. The platform encrypts values at rest. You can reference secrets defined here in environment variables, scale rules, volume mounts, and Dapr components.
46
46
47
-
### [Portal](#tab/in-place+portal)
47
+
### [Portal](#tab/portal)
48
48
49
49
1. Go to your Functions container app in the [Azure portal](https://portal.azure.com).
50
50
@@ -62,7 +62,7 @@ Container Apps stores secrets in the app's `configuration.secrets` array. The pl
62
62
63
63
1. Select **Add**.
64
64
65
-
### [Azure CLI](#tab/in-place+cli)
65
+
### [Azure CLI](#tab/cli)
66
66
67
67
Add a secret when you create your Functions container app:
68
68
@@ -91,7 +91,7 @@ az containerapp secret set \
91
91
92
92
After you store a secret, reference it in an environment variable so your function code can read it.
93
93
94
-
### [Portal](#tab/in-place+portal)
94
+
### [Portal](#tab/portal)
95
95
96
96
1. In your Functions container app, under *Application*, select **Revisions and replicas**.
97
97
@@ -111,7 +111,7 @@ After you store a secret, reference it in an environment variable so your functi
111
111
112
112
1. Select **Save**, and then select **Create** to deploy the new revision.
113
113
114
-
### [Azure CLI](#tab/in-place+cli)
114
+
### [Azure CLI](#tab/cli)
115
115
116
116
```azurecli
117
117
az containerapp update \
@@ -122,9 +122,9 @@ az containerapp update \
122
122
123
123
---
124
124
125
-
## Verify the secret
125
+
## Verify the Container Apps secret
126
126
127
-
Confirm your function can read the secret value by invoking the function and checking that it runs without errors related to missing configuration.
127
+
Confirm your function can read the secret valueby invoking the function and checking that it runs without errors related to missing configuration.
Your container app needs a managed identity to authenticate to Key Vault without credentials.
150
150
151
-
### [Portal](#tab/keyvault+portal)
151
+
### [Portal](#tab/portal)
152
152
153
153
1. Go to your Functions container app in the [Azure portal](https://portal.azure.com).
154
154
@@ -158,7 +158,7 @@ Your container app needs a managed identity to authenticate to Key Vault without
158
158
159
159
1. Select **Save**, and then select **Yes** to confirm.
160
160
161
-
### [Azure CLI](#tab/keyvault+cli)
161
+
### [Azure CLI](#tab/cli)
162
162
163
163
```azurecli
164
164
az containerapp identity assign \
@@ -173,7 +173,7 @@ az containerapp identity assign \
173
173
174
174
Assign the **Key Vault Secrets User** role to the managed identity so it can read secrets.
175
175
176
-
### [Portal](#tab/keyvault+portal)
176
+
### [Portal](#tab/portal)
177
177
178
178
1. Go to your Key Vault in the [Azure portal](https://portal.azure.com).
179
179
@@ -191,7 +191,7 @@ Assign the **Key Vault Secrets User** role to the managed identity so it can rea
191
191
192
192
1. Select **Review + assign**.
193
193
194
-
### [Azure CLI](#tab/keyvault+cli)
194
+
### [Azure CLI](#tab/cli)
195
195
196
196
```azurecli
197
197
PRINCIPAL_ID=$(az containerapp show \
@@ -215,7 +215,7 @@ az role assignment create \
215
215
216
216
## Store a secret in Key Vault
217
217
218
-
### [Portal](#tab/keyvault+portal)
218
+
### [Portal](#tab/portal)
219
219
220
220
1. In your Key Vault, under *Objects*, select **Secrets**.
221
221
@@ -235,7 +235,7 @@ az role assignment create \
235
235
236
236
1. Copy the **Secret Identifier** URI. Use the versionless URI (without the trailing version segment) to enable automatic rotation.
237
237
238
-
### [Azure CLI](#tab/keyvault+cli)
238
+
### [Azure CLI](#tab/cli)
239
239
240
240
```azurecli
241
241
az keyvault secret set \
@@ -258,7 +258,7 @@ echo $SECRET_URI
258
258
259
259
Create a Container Apps secret that references the Key Vault secret, then bind it to an environment variable.
260
260
261
-
### [Portal](#tab/keyvault+portal)
261
+
### [Portal](#tab/portal)
262
262
263
263
1. Go to your Functions container app. Under *Settings*, select **Secrets**.
264
264
@@ -277,7 +277,7 @@ Create a Container Apps secret that references the Key Vault secret, then bind i
277
277
278
278
1. Under *Application*, select **Revisions and replicas**. Create a new revision with the environment variable `DATABASE_PASSWORD` referencing the `database-password` secret.
279
279
280
-
### [Azure CLI](#tab/keyvault+cli)
280
+
### [Azure CLI](#tab/cli)
281
281
282
282
For system-assigned identity:
283
283
@@ -308,7 +308,7 @@ az containerapp update \
308
308
309
309
---
310
310
311
-
## Verify the secret
311
+
## Verify the Key Vault secret
312
312
313
313
Invoke your function and confirm it runs without errors related to missing configuration:
0 commit comments