Adding how to use deployment output info to README #11148
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
anuragc617
changed the title
| @@ -73,6 +73,28 @@ The following parameters are shown when the selected action is to create or upda | |||
|
|
|||
| * **Deployment Mode**: This specifies the [deployment mode](https://azure.microsoft.com/en-us/documentation/articles/resource-group-template-deploy) in which the Azure resources specified in the template have to be deployed. Incremental mode handles deployments as incremental updates to the resource group . It leaves unchanged resources that exist in the resource group but are not specified in the template. Complete mode deletes resources that are not in your template. [Validate mode](https://msdn.microsoft.com/en-us/library/azure/dn790547.aspx) enables you to find syntactical problems with the template before creating actual resources. By default, incremental mode is used. | |||
|
|
|||
| ### Deployment Outputs: | |||
| It is the output of the deployment object created using Azure Resource Manager templates which can be used in the subsequent tasks like Powershell and Azure CLI. | |||
There was a problem hiding this comment.
Re-word to "Outputs created by Azure Resource Manager template deployment. It can be used in subsequent tasks (like Azure Powershell or Azure CLI) for further processing."
| ``` | ||
| $var=ConvertFrom-Json '$(storageAccountName)' | ||
| $value=$var.storageAccountName.value | ||
| Write-Host "##vso[task.setvariable variable=value;]$value" |
There was a problem hiding this comment.
Write-Host "##vso[task.setvariable variable=storageAccount;]$value"
|
|
||
| Example: | ||
| ``` | ||
| var=`echo "$(storageAccountName)" | sed -e 's/}/"\n}/g' | sed -e 's/{/{\n"/g' | sed -e 's/:/":"/g' | sed -e 's/,/",\n"/g' | sed -e 's/"}/}/g' | sed -e 's/}"/}/g' | sed -e 's/"{/{/g' | sed -e 's/\[/\[\n"/g' | sed -e 's/]/"\n]/g' | sed -e 's/"\[/\[/g' | sed -e 's/]"/]/g'` |
| It is the output of the deployment object created using Azure Resource Manager templates which can be used in the subsequent tasks like Powershell and Azure CLI. | ||
|
|
||
| **How to use Deployment output** | ||
| The deployment output can be parsed to JSON object using "ConvertFrom-Json" PowerShell cmdlet in Poweshell task and then that object can be used in other tasks. |
There was a problem hiding this comment.
Suggested change
| The deployment output can be parsed to JSON object using "ConvertFrom-Json" PowerShell cmdlet in Poweshell task and then that object can be used in other tasks. | |
| The deployment output can be parsed to JSON object using "ConvertFrom-Json" PowerShell cmdlet in Powershell/Azure Poweshell task and then that object can be used in same task or subsequent tasks. |
| Write-Host "##vso[task.setvariable variable=value;]$value" | ||
| ``` | ||
|
|
||
| On linux agent if you want to use deployment output in Azure CLI task, you can avoid extra Powershell task by adding double quotes to convert it to valid JSON. This is needed because Azure CLI task on linux uses bash and the bash removes the double quotes of JSON string making it invalid JSON. |
There was a problem hiding this comment.
Suggested change
| On linux agent if you want to use deployment output in Azure CLI task, you can avoid extra Powershell task by adding double quotes to convert it to valid JSON. This is needed because Azure CLI task on linux uses bash and the bash removes the double quotes of JSON string making it invalid JSON. | |
| On linux based agents, same technique of Powershell task can be used to create a JSON variable. However, if you want to avoid Powershell task, you can use a script similar to below which converts the Outputs to valid JSON by adding double quotes. |
| @@ -73,6 +73,39 @@ The following parameters are shown when the selected action is to create or upda | |||
|
|
|||
| * **Deployment Mode**: This specifies the [deployment mode](https://azure.microsoft.com/en-us/documentation/articles/resource-group-template-deploy) in which the Azure resources specified in the template have to be deployed. Incremental mode handles deployments as incremental updates to the resource group . It leaves unchanged resources that exist in the resource group but are not specified in the template. Complete mode deletes resources that are not in your template. [Validate mode](https://msdn.microsoft.com/en-us/library/azure/dn790547.aspx) enables you to find syntactical problems with the template before creating actual resources. By default, incremental mode is used. | |||
|
|
|||
| ### Deployment Outputs: | |||
There was a problem hiding this comment.
please add a link to this section in task.json input helptext
bishal-pdMSFT
approved these changes
Aug 20, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.