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/virtual-machines/linux/image-builder-json.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1751,9 +1751,9 @@ Size of the proxy virtual machine used to pass traffic to the build VM and valid
1751
1751
1752
1752
## Properties: autoRun
1753
1753
1754
-
You can use the `autoRun` property to control whether the image template build process should automatically start when the template is created or updated. It's an enum with two possible values:
1755
-
-**Enabled** - Auto run is enabled, so your image template build process will automatically start when the template is created or updated.
1756
-
-**Disabled** - Auto run is disabled, so you will have to manually start the image build process after the template is created or updated.
1754
+
You can use the `autoRun` property to control whether the image template build process should automatically start when the template is created. It's an enum with two possible values:
1755
+
-**Enabled** - Auto run is enabled, so your image template build process will automatically start when the template is created.
1756
+
-**Disabled** - Auto run is disabled, so you will have to manually start the image build process after the template is created.
1757
1757
1758
1758
```json
1759
1759
"properties": {
@@ -1762,11 +1762,11 @@ You can use the `autoRun` property to control whether the image template build p
1762
1762
```
1763
1763
1764
1764
> [!NOTE]
1765
-
> When you set `autoRun` to "Enabled," the image build process runs **once** upon template creation or update. It ensures that the initial image build occurs seamlessly. However, it does not provide consistent and ongoing image builds. For consistent and ongoing image builds that run once an image template is updated, see [How to use Azure Image Builder triggers to set up an automatic image build](../image-builder-triggers-how-to.md).
1765
+
> When you set `autoRun` to "Enabled," the image build process runs **once** upon template creation. It ensures that the initial image build occurs seamlessly. However, it does not provide consistent and ongoing image builds. For consistent and ongoing image builds that run once an image template is updated, see [How to use Azure Image Builder triggers to set up an automatic image build](../image-builder-triggers-how-to.md).
1766
1766
>
1767
1767
> Unlike `autoRun`, automatic image creation via the Azure Image Builder trigger resource ensures that image builds occur consistently. Whenever there are changes to the template, the Azure Image Builder service will automatically trigger the image build process.
1768
1768
>
1769
-
> Choose `autoRun` for immediate image builds upon template creation or update. Opt for automatic image creation when you need ongoing consistency in image builds. Consider your specific requirements and use the appropriate option based on your workflow.
1769
+
> Choose `autoRun` for immediate image builds upon template creation. Opt for automatic image creation when you need ongoing consistency in image builds. Consider your specific requirements and use the appropriate option based on your workflow.
0 commit comments