Skip to content

Commit 4df4e30

Browse files
committed
added two new procedures
1 parent 2c15c80 commit 4df4e30

File tree

5 files changed

+17
-3
lines changed

5 files changed

+17
-3
lines changed
1.77 MB
Loading
1.77 MB
Loading
1.77 MB
Loading
1.77 MB
Loading

articles/automation/how-to/runbook-authoring-extension-for-vscode.md

Lines changed: 17 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,10 @@
11
---
22
title: Azure Automation extension for Visual Studio Code
33
description: Learn how to use the Azure Automation extension for Visual Studio Code to author runbooks.
4-
ms.date: 12/18/2022
4+
ms.date: 01/06/2023
55
ms.topic: how-to
66
---
77

8-
98
# Use Azure Automation extension for Visual Studio Code
109

1110
This article explains about the Visual Studio that you can use to create and manage runbooks. You can perform all runbook management operations such as creating runbooks, editing runbook, triggering a job, tracking recent jobs outputs, linking a schedule and asset management.
@@ -73,7 +72,7 @@ To run the Automation job, follow these steps:
7372
1. In Automation account, select the runbook.
7473
1. Right click and select **Start Automation job** to run the Automation job.
7574

76-
:::image type="content" source="media/runbook-authoring-extension-for-vscode/start-automation-job-inline.png" alt-text="Screenshot on how to run local version of job using the Azure Automation extension." lightbox="media/runbook-authoring-extension-for-vscode/start-automation-job-expanded.png":::
75+
:::image type="content" source="media/runbook-authoring-extension-for-vscode/start-automation-job-inline.png" alt-text="Screenshot on how to run Automation job using the Azure Automation extension." lightbox="media/runbook-authoring-extension-for-vscode/start-automation-job-expanded.png":::
7776

7877
### Add new webhook
7978

@@ -107,6 +106,21 @@ To add a webhook to the runbook, follow these steps:
107106

108107
A notification appears that the variable is created, you can view the new variable in **fx Variables** option.
109108

109+
### Run local in debug mode
110+
1. In Automation account, go to **Runbooks** and select a runbook.
111+
1. In the edit pane, add the break point.
112+
1. Right click on the runbook and select **Run local in Debug Mode**.
113+
114+
:::image type="content" source="media/runbook-authoring-extension-for-vscode/run-local-debug-mode-inline.png" alt-text="Screenshot that shows the running of local runbook in debug mode." lightbox="media/runbook-authoring-extension-for-vscode/add-new-webhook-expanded.png":::
115+
116+
### Compare local runbook
117+
1. In Automation account, go to **Runbooks** and select a runbook
118+
1. Right click on the runbook and select **Compare local runbook**.
119+
1. In the edit pane, you will see the information in two layouts - runbook copy and published/draft copy.
120+
>[!NOTE]
121+
>If the runbook is **InEdit** mode, you will have to select either the Compare Published content or Compare Draft content to compare.
122+
123+
:::image type="content" source="media/runbook-authoring-extension-for-vscode/compare-local-runbook-inline.png" alt-text="Screenshot that shows how to compare local runbook." lightbox="media/runbook-authoring-extension-for-vscode/compare-local-runbook-expanded.png":::
110124

111125
## Next steps
112126

0 commit comments

Comments
 (0)