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/container-apps/get-started-existing-container-image.md
+10-3Lines changed: 10 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,6 +41,8 @@ Now that you have an environment created, you can deploy your first container ap
41
41
42
42
::: zone pivot="container-apps-private-registry"
43
43
44
+
TODO1 Replace these H3s with a numbered list?
45
+
44
46
### Set environment variables
45
47
46
48
Replace the \<PLACEHOLDERS\> with your values. Your user principal name will typically be in the format of an email address (for example, `[email protected]`).
TODO1 Explain why you should use a key vault to store your registry password. We could just link to one of the quickstarts below on creating a key vault and storing a secret in it, and only include the command for retrieving the secret here.
77
+
74
78
# [Bash](#tab/bash)
75
79
76
80
```bash
@@ -105,17 +109,20 @@ az role assignment create --role "Key Vault Secrets Officer" --assignee "$USER_P
0 commit comments