File tree Expand file tree Collapse file tree 1 file changed +6
-5
lines changed Expand file tree Collapse file tree 1 file changed +6
-5
lines changed Original file line number Diff line number Diff line change @@ -34,7 +34,7 @@ Next, add the required Azure CLI extensions.
34
34
35
35
``` azurecli-interactive
36
36
az extension add --upgrade --yes --name customlocation
37
- az extension remove --name containerapps
37
+ az extension remove --name containerapp
38
38
az extension add -s https://download.microsoft.com/download/5/c/2/5c2ec3fc-bd2a-4615-a574-a1b7c8e22f40/containerapp-0.0.1-py2.py3-none-any.whl --yes
39
39
```
40
40
@@ -77,15 +77,17 @@ A connected environment is largely the same as a standard Container Apps environ
77
77
78
78
``` azure-interactive
79
79
myContainerApp="my-container-app"
80
- myConnectedEnvironment=$(az containerapp connected-env list --custom-location $customLocationId -o tsv --query '[].id')
80
+ myConnectedEnvironmentName="<NAME_OF_CONNECTED_ENVIRONMENT>"
81
+ myConnectedEnvironmentResourceGroup="<RESOURCE_GROUP_NAME_OF_CONNECTED_ENVIRONMENT>"
82
+ myConnectedEnvironment=$(az containerapp connected-env show --resource-group $myConnectedEnvironmentResourceGroup --name $myConnectedEnvironmentName -o tsv --query id)
81
83
```
82
84
83
85
## Create an app
84
86
85
87
The following example creates a Node.js app.
86
88
87
89
``` azurecli-interactive
88
- az container app create \
90
+ az containerapp create \
89
91
--resource-group $myResourceGroup \
90
92
--name $myContainerApp \
91
93
--environment $myConnectedEnvironment \
@@ -94,8 +96,7 @@ The following example creates a Node.js app.
94
96
--target-port 80 \
95
97
--ingress 'external'
96
98
97
- az containerapp browse --resource-group $myResourceGroup \
98
- --name $myContainerApp
99
+ az containerapp browse --resource-group $myResourceGroup --name $myContainerApp
99
100
```
100
101
101
102
## Get diagnostic logs using Log Analytics
You can’t perform that action at this time.
0 commit comments