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/deployment-environments/concept-environment-yaml.md
+15-15Lines changed: 15 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,28 +1,28 @@
1
1
---
2
-
title: manifest.yaml schema
3
-
description: Learn how to use manifest.yaml to define parameters in your environment definition.
2
+
title: environment.yaml schema
3
+
description: Learn how to use environment.yaml to define parameters in your environment definition.
4
4
author: RoseHJM
5
5
ms.author: rosemalcolm
6
6
ms.service: azure-deployment-environments
7
7
ms.topic: concept-article
8
8
ms.date: 03/20/2025
9
9
10
-
# Customer intent: As a developer, I want to know the properties and parameters that I can use in manifest.yaml.
10
+
# Customer intent: As a developer, I want to know the properties and parameters that I can use in environment.yaml.
11
11
12
12
---
13
13
14
-
# Properties and parameters in manifest.yaml
14
+
# Properties and parameters in environment.yaml
15
15
16
-
Azure Deployment Environments environment definitions are infrastructure as code (IaC) that are written in Bicep or Terraform and stored in repositories. You can modify and adapt environment definitions for your requirements and then use them to create a deployment environment on Azure. The manifest.yaml schema defines and describes the types of Azure resources included in environment definitions.
16
+
Azure Deployment Environments environment definitions are infrastructure as code (IaC) that are written in Bicep or Terraform and stored in repositories. You can modify and adapt environment definitions for your requirements and then use them to create a deployment environment on Azure. The environment.yaml schema defines and describes the types of Azure resources included in environment definitions.
17
17
18
18
19
-
## What is manifest.yaml?
19
+
## What is environment.yaml?
20
20
21
-
The manifest.yaml file describes the resources used and the template location for the environment definition.
21
+
The environment.yaml file describes the resources used and the template location for the environment definition.
22
22
23
-
### Sample manifest.yaml
23
+
### Sample environment.yaml
24
24
25
-
The following script is an example of the manifest.yaml that's required for your environment definition.
25
+
The following script is an example of the environment.yaml that's required for your environment definition.
26
26
27
27
```yml
28
28
name: WebApp
@@ -35,7 +35,7 @@ templatePath: azuredeploy.json
35
35
36
36
### Definitions
37
37
38
-
The following table describes the properties that you can use in manifest.yaml.
38
+
The following table describes the properties that you can use in environment.yaml.
39
39
40
40
| Property | Type | Description | Required?|Example|
@@ -47,13 +47,13 @@ The following table describes the properties that you can use in manifest.yaml.
47
47
| `templatePath` | string | The relative path of the entry template file. | Yes | main.tf </br> main.bicep </br> azuredeploy.json |
48
48
| `parameters` | array | Input parameters to use when creating the environment and running actions. | No | #/definitions/Parameter |
49
49
50
-
## Parameters in manifest.yaml
50
+
## Parameters in environment.yaml
51
51
52
52
Parameters enable you to reuse an environment definition in different scenarios. For example, you might want developers in different regions to deploy the same environment. You can define a location parameter to prompt developers to enter the desired location as they create their environments.
53
53
54
-
### Sample manifest.yaml with parameters
54
+
### Sample environment.yaml with parameters
55
55
56
-
The following script is an example of a manifest.yaml file that includes two parameters: `location`and `name`.
56
+
The following script is an example of a environment.yaml file that includes two parameters: `location`and `name`.
57
57
58
58
```yml
59
59
name: WebApp
@@ -78,7 +78,7 @@ parameters:
78
78
79
79
### Parameter definitions
80
80
81
-
The following table describes the data types that you can use in manifest.yaml. The data type names used in the manifest.yaml file differ from the ones used in ARM templates.
81
+
The following table describes the data types that you can use in environment.yaml. The data type names used in the environment.yaml file differ from the ones used in ARM templates.
82
82
83
83
Each parameter can use any of the following properties:
84
84
@@ -95,7 +95,7 @@ Each parameter can use any of the following properties:
95
95
96
96
## YAML schema
97
97
98
-
There's a defined schema for Azure Deployment Environments manifest.yaml files. It can make editing these files a little easier. You can add the schema definition to the beginning of your manifest.yaml file:
98
+
There's a defined schema for Azure Deployment Environments environment.yaml files. It can make editing these files a little easier. You can add the schema definition to the beginning of your environment.yaml file:
0 commit comments