Skip to content

Commit e954dcc

Browse files
authored
Merge pull request #49954 from spelluru/labenv0824
added a section for public env
2 parents 38744cb + e002a9e commit e954dcc

File tree

1 file changed

+6
-8
lines changed

1 file changed

+6
-8
lines changed

articles/lab-services/devtest-lab-create-environment-from-arm.md

Lines changed: 6 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -33,10 +33,11 @@ Learn more about the many [benefits of using Resource Manager templates](https:/
3333
> [!NOTE]
3434
> When you use a Resource Manager template as a basis to create more lab VMs, there are some differences to keep in mind whether you are creating Multi-VMs or single-VMs. [Use a virtual machine's Azure Resource Manager template](devtest-lab-use-resource-manager-template.md) explains these differences in greater detail.
3535
>
36-
>
3736
38-
## Configure Azure Resource Manager template repositories
37+
## DevTest Labs public environments
38+
Azure DevTest Labs has a [public repository of Azure Resource Manager templates](https://github.com/Azure/azure-devtestlab/tree/master/Environments) that you can use to create environments without having to connect to an external GitHub source by yourself. This repository includes frequently used templates such as Azure Web Apps, Service Fabric Cluster, and development SharePoint Farm environment. This feature is similar to the public repository of artifacts that is included for every lab that you create. The environment repository allows you to quickly get started with pre-authored environment templates with minimum input parameters to provide you with a smooth getting started experience for PaaS resources within labs. For more information, see [Configure and use public environments in DevTest Labs](devtest-lab-configure-use-public-environments.md).
3939

40+
## Configure your own template repositories
4041
As one of the best practices with infrastructure-as-code and configuration-as-code, environment templates should be managed in source control. Azure DevTest Labs follows this practice and loads all Azure Resource Manager templates directly from your GitHub or VSTS Git repositories. As a result, Resource Manager templates can be used across the entire release cycle, from the test environment to the production environment.
4142

4243
Check out the templates created by the DevTest Labs team in the [public GitHub repository](https://github.com/Azure/azure-devtestlab/tree/master/Environments). In this public repository, you can view templates shared by others that you can use directly or customize them to suit your needs. After you create your template, store it in this repository to share it with others. You can also set up your own Git repository with templates that can be used to set up environments in the cloud.
@@ -52,12 +53,9 @@ There are a couple of rules to follow to organize your Azure Resource Manager te
5253
- Metadata can be defined to specify the template display name and description. This metadata must be in a file named `metadata.json`. The following example metadata file illustrates how to specify the display name and description:
5354

5455
```json
55-
{
56-
57-
"itemDisplayName": "<your template name>",
58-
59-
"description": "<description of the template>"
60-
56+
{
57+
"itemDisplayName": "<your template name>",
58+
"description": "<description of the template>"
6159
}
6260
```
6361

0 commit comments

Comments
 (0)