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: CONTRIBUTING.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,13 +10,15 @@ We've added some guideliness to help you in your quest. Please read and feel fre
10
10
4. Let us know if you have any questions or you're unsure of something
11
11
5. Please fork the project and create a new branch to commit your work
12
12
6. DO NOT push to master. If you don't know what this means, refresh your memory [here](https://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell)
13
+
7. We use [App Insights](https://azure.microsoft.com/en-us/services/application-insights/) to track telemetry and ask that you make use of the `telemetry` module to capture telemetry on features you add.
13
14
14
15
## Setting up the project locally
15
16
1. Ensure you have Node.js installed. Get it [here](https://nodejs.org/en/)
16
17
2. Ensure you have Visual Studio Code installed. Get it [here](https://code.visualstudio.com/Download)
17
18
3. Ensure you have Git installed. Get it [here](https://git-scm.com/download)
18
19
4. Open the command line of your choice and navigate to the root of the project folder
19
20
5. Run `npm install` to install the npm packages necessary to run the project
21
+
6. Edit the `constants.js` file and provide your own Instrumentation Key to use during development so you can see how your telemetry is coming in. Prior to being deployed to the marketplace, I'll update this to be the production key.
20
22
21
23
## Testing your code changes
22
24
At the moment we don't have automated tests. Trust us, we're working on it. However, you're more than welcome to contribute if you've got time or feel you're up to the task. To test your code changes, launch the debugger from within VS Code. This will launch a separate instance of VS Code with the extension already installed. Step through the code as you would do norrmally.
Copy file name to clipboardExpand all lines: README.md
+30-6Lines changed: 30 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,15 +2,33 @@
2
2
3
3
This extension for [Visual Studio Code](http://code.visualstudio.com) gives Azure developers some convenient commands for creating or accessing resources directly in the editor.
4
4
5
-
## New in v1.1.0
5
+
## New in v1.2.0
6
+
Here's a brief summary of the new features included in the 1.2.0 release.
6
7
7
-
-**Azure Key Vault creation.**
8
+
### Export Template
8
9
9
-
You can now use the Azure Tools for Visual Studio Code to create new Key Vault instances. Selecting the **Create Key Vault** command. Then you can create a new or select an existing resource group into which your new Key Vault will be created.
10
+
In 1.2.0 we've added support for exporting existing resource groups to ARM templates saved in your workspace. First, you invoke the `Export` command using the palette.

17
+
18
+
A few seconds later, the resource group's contents are downloaded as an ARM template and stored into your current workspace's `arm-templates` folder.
19
+
20
+

21
+
22
+
> **Note:** As of the 1.2.0 release time frame there are a few kinks in the particular Azure API call we're using; certain details of your resources might not be persisted exactly right. You can use the great features contained in the [Azure Resource Manager Tools extension](https://marketplace.visualstudio.com/items?itemName=msazurermtools.azurerm-vscode-tools) (which bundled with this extension) to make tweaks. The API owners are working on making great improvements to this functionality so it'll improve in future releases of the back-end API.
23
+
24
+
### Azure Batch account creation
25
+
26
+
From within Visual Studio Code you can use the `Create Azure Batch` command from the palette, shown below, to create new Azure Batch accounts. Future releases may add support for scripting against your Batch account, creating Jobs, and so forth. Feel free to send the team requests for additional Batch features via our [GitHub Issues page](https://github.com/bradygaster/azure-tools-vscode/issues).
- Search the [Azure QuickStart Templates](https://github.com/Azure/azure-quickstart-templates) GitHub repository
15
33
- Download Azure Resource Manager (ARM) template and parameter files to workspace
16
34
- Uses the [Azure Resource Manager Tools](https://marketplace.visualstudio.com/items?itemName=msazurermtools.azurerm-vscode-tools) extension to simplify the template-editing experience
@@ -30,8 +48,14 @@ Each of these commands is visible directly from commands visible in the command
30
48
31
49

32
50
33
-
## New Azure Resource Manager (ARM) Features
34
-
**New in 1.0.0** - Now you can use keyword searches to find one of the numerous existing templates in the Azure QuickStart Templates repository, then download the templates you find and deploy them **all within Visual Studio Code**.
51
+
## Azure Key Vault creation
52
+
53
+
You can now use the Azure Tools for Visual Studio Code to create new Key Vault instances. Selecting the **Create Key Vault** command. Then you can create a new or select an existing resource group into which your new Key Vault will be created.
You can use keyword searches to find one of the numerous existing templates in the Azure QuickStart Templates repository, then download the templates you find and deploy them **all within Visual Studio Code**.
35
59
36
60
### Search and Download from the Azure Template QuickStart Repository
37
61
Templates in the QuickStart repository are easily searchable from within Visual Studio Code.
0 commit comments