Skip to content

Commit 6b11f2d

Browse files
Merge pull request #234126 from divargas-msft/patch-1
[Doc-a-thon] Updating image-builder-json.md
2 parents c149b86 + 141e146 commit 6b11f2d

File tree

1 file changed

+9
-9
lines changed

1 file changed

+9
-9
lines changed

articles/virtual-machines/linux/image-builder-json.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn how to create a Bicep file or ARM JSON template to use with A
44
author: kof-f
55
ms.author: kofiforson
66
ms.reviewer: erd
7-
ms.date: 03/15/2023
7+
ms.date: 04/11/2023
88
ms.topic: reference
99
ms.service: virtual-machines
1010
ms.subservice: image-builder
@@ -677,7 +677,7 @@ If there's an error trying to download the file, or put it in a specified direct
677677

678678
### Windows update customizer
679679

680-
The `WindowsUpdate` customizer is built on the [community Windows Update Provisioner](https://packer.io/docs/provisioners/community-supported.html) for Packer, which is an open source project maintained by the Packer community. Microsoft tests and validate the provisioner with the Image Builder service, and will support investigating issues with it, and work to resolve issues, however the open source project isn't officially supported by Microsoft. For detailed documentation on and help with the Windows Update Provisioner, see the project repository.
680+
The `WindowsUpdate` customizer is built on the [community Windows Update Provisioner](https://developer.hashicorp.com/packer/docs/provisioners/community-supported) for Packer, which is an open source project maintained by the Packer community. Microsoft tests and validate the provisioner with the Image Builder service, and will support investigating issues with it, and work to resolve issues, however the open source project isn't officially supported by Microsoft. For detailed documentation on and help with the Windows Update Provisioner, see the project repository.
681681

682682
# [JSON](#tab/json)
683683

@@ -735,7 +735,7 @@ If Azure Image Builder creates a Windows custom image successfully, and you crea
735735

736736
#### Default Sysprep command
737737

738-
```powershell
738+
```azurepowershell-interactive
739739
Write-Output '>>> Waiting for GA Service (RdAgent) to start ...'
740740
while ((Get-Service RdAgent).Status -ne 'Running') { Start-Sleep -s 5 }
741741
Write-Output '>>> Waiting for GA Service (WindowsAzureTelemetryService) to start ...'
@@ -791,7 +791,7 @@ You can distribute an image to both of the target types in the same configuratio
791791
792792
Because you can have more than one target to distribute to, Image Builder maintains a state for every distribution target that can be accessed by querying the `runOutputName`. The `runOutputName` is an object you can query post distribution for information about that distribution. For example, you can query the location of the VHD, or regions where the image version was replicated to, or SIG Image version created. This is a property of every distribution target. The `runOutputName` must be unique to each distribution target. Here's an example for querying an Azure Compute Gallery distribution:
793793

794-
```azurecli
794+
```azurecli-interactive
795795
subscriptionID=<subcriptionID>
796796
imageResourceGroup=<resourceGroup of image template>
797797
runOutputName=<runOutputName>
@@ -803,7 +803,7 @@ az resource show \
803803

804804
Output:
805805

806-
```json
806+
```output
807807
{
808808
"id": "/subscriptions/xxxxxx/resourcegroups/rheltest/providers/Microsoft.VirtualMachineImages/imageTemplates/ImageTemplateLinuxRHEL77/runOutputs/rhel77",
809809
"identity": null,
@@ -1423,11 +1423,11 @@ vnetConfig: {
14231423

14241424
To start a build, you need to invoke 'Run' on the Image Template resource, examples of `run` commands:
14251425

1426-
```PowerShell
1426+
```azurepowershell-interactive
14271427
Invoke-AzResourceAction -ResourceName $imageTemplateName -ResourceGroupName $imageResourceGroup -ResourceType Microsoft.VirtualMachineImages/imageTemplates -ApiVersion "2021-10-01" -Action Run -Force
14281428
```
14291429

1430-
```azurecli
1430+
```azurecli-interactive
14311431
az resource invoke-action \
14321432
--resource-group $imageResourceGroup \
14331433
--resource-type Microsoft.VirtualMachineImages/imageTemplates \
@@ -1443,11 +1443,11 @@ The build can be canceled anytime. If the distribution phase has started you can
14431443

14441444
Examples of `cancel` commands:
14451445

1446-
```powerShell
1446+
```azurepowershell-interactive
14471447
Invoke-AzResourceAction -ResourceName $imageTemplateName -ResourceGroupName $imageResourceGroup -ResourceType Microsoft.VirtualMachineImages/imageTemplates -ApiVersion "2021-10-01" -Action Cancel -Force
14481448
```
14491449

1450-
```azurecli
1450+
```azurecli-interactive
14511451
az resource invoke-action \
14521452
--resource-group $imageResourceGroup \
14531453
--resource-type Microsoft.VirtualMachineImages/imageTemplates \

0 commit comments

Comments
 (0)