From 3a33afcd070bc31ae53740b9a6e1b722142b0ce9 Mon Sep 17 00:00:00 2001 From: David Michelman Date: Wed, 15 Jul 2020 11:59:54 -0700 Subject: [PATCH] Change `az group deployment` to `az deployment group` The command `az group deployment create` is deprecated. It creates this message: This command is implicitly deprecated because command group 'group deployment' is deprecated and will be removed in a future release. Use 'deployment group' instead. --- docs/solution-onboarding.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/solution-onboarding.md b/docs/solution-onboarding.md index 04573876..bddbdfc8 100644 --- a/docs/solution-onboarding.md +++ b/docs/solution-onboarding.md @@ -43,7 +43,7 @@ az cloud set --name az login az account set --subscription "" # execute deployment command to add container insights solution to the specified log analytics workspace -az group deployment create --resource-group --template-file ./azuremonitor-containerSolution.json --parameters @./azuremonitor-containerSolutionParams.json +az deployment group create --resource-group --template-file ./azuremonitor-containerSolution.json --parameters @./azuremonitor-containerSolutionParams.json ``` The configuration change can take a few minutes to complete. When it finishes, you see a message similar to the following that includes the result: @@ -52,4 +52,4 @@ The configuration change can take a few minutes to complete. When it finishes, y provisioningState : Succeeded ``` -After monitoring is enabled, it can take around 15 minutes before you are able to see operational data for the cluster. \ No newline at end of file +After monitoring is enabled, it can take around 15 minutes before you are able to see operational data for the cluster.