Revised references to ARM, updated Terraform runner paragraph & examples.

RoseHJM · RoseHJM · commit 040d4a0b427b · 2024-04-15T18:49:43.000-07:00
diff --git a/articles/deployment-environments/configure-environment-definition.md b/articles/deployment-environments/configure-environment-definition.md
@@ -19,17 +19,17 @@ In Azure Deployment Environments, you can use a [catalog](concept-environments-k
 
 An environment definition is composed of least two files:
 
-- An [Azure Resource Manager template (ARM template)](../azure-resource-manager/templates/overview.md) in JSON file format. For example, *azuredeploy.json*.
+- A template from an IaC framework. For example:
+    - An Azure Resource Manager (ARM) template might use a file called *azuredeploy.json*.
+    - A Bicep template might use a file called *azuredeploy.bicep*.
+    - A Terraform template might use a file called *azuredeploy.tf*, or *azuredeploy.tf.json*.
 - A configuration file that provides metadata about the template. This file should be named *environment.yaml*.
 
->[!NOTE]
-> Azure Deployment Environments currently supports only ARM templates.
-
 Your development teams use the environment definitions that you provide in the catalog to deploy environments in Azure.
 
 Microsoft offers a [sample catalog](https://aka.ms/deployment-environments/SampleCatalog) that you can use as your repository. You can also use your own private repository, or you can fork and customize the environment definitions in the sample catalog.
 
-After you [add a catalog](how-to-configure-catalog.md) to your dev center, the service scans the specified folder path to identify folders that contain an ARM template and an associated environment file. The specified folder path should be a folder that contains subfolders that hold the environment definition files.
+After you [add a catalog](how-to-configure-catalog.md) to your dev center, the service scans the specified folder path to identify folders that contain a template and an associated environment file. The specified folder path should be a folder that contains subfolders that hold the environment definition files.
 
 In this article, you learn how to:
 
@@ -51,20 +51,13 @@ To add an environment definition:
 
 1. Add two files to the new repository subfolder:
 
-   - An ARM template as a JSON file.
-
-      To implement IaC for your Azure solutions, use ARM templates. [ARM templates](../azure-resource-manager/templates/overview.md) help you define the infrastructure and configuration of your Azure solution and repeatedly deploy it in a consistent state.
-
-      To learn how to get started with ARM templates, see the following articles:
-
-      - [Understand the structure and syntax of ARM templates](../azure-resource-manager/templates/syntax.md): Describes the structure of an ARM template and the properties that are available in the different sections of a template.
-      - [Use linked templates](../azure-resource-manager/templates/linked-templates.md?tabs=azure-powershell#use-relative-path-for-linked-templates): Describes how to use linked templates with the new ARM template `relativePath` property to easily modularize your templates and share core components between environment definitions.
+   - An IaC template file.
 
    - An environment as a YAML file.
 
-      The *environment.yaml* file contains metadata related to the ARM template.
+      The *environment.yaml* file contains metadata related to the IaC template.
 
-       The following script is an example of the contents of an *environment.yaml* file:
+       The following script is an example of the contents of an *environment.yaml* file for an ARM template:
 
        ```yaml
            name: WebApp
@@ -73,10 +66,18 @@ To add an environment definition:
            description: Deploys a web app in Azure without a datastore
            runner: ARM
            templatePath: azuredeploy.json
-        ```  
-  
-       > [!NOTE]
-       > The `version` field is optional. Later, the field will be used to support multiple versions of environment definitions.
+       ```  
+
+      Use the following table to understand the fields in the *environment.yaml* file:
+
+      | Field | Description |
+      |-------|-------------|
+      | name | The name of the environment definition. |
+      | version | The version of the environment definition. This field is optional. |
+      | summary | A brief description of the environment definition. |
+      | description | A detailed description of the environment definition. |
+      | runner | The IaC framework that the template uses. The value can be `ARM` or `Bicep`. You can also specify a path to a template stored in a a container registry. |
+      | templatePath | The path to the IaC template file. |
 
       :::image type="content" source="../deployment-environments/media/configure-environment-definition/create-subfolder-path.png" alt-text="Screenshot that shows a folder path with a subfolder that contains an ARM template and an environment file." lightbox="../deployment-environments/media/configure-environment-definition/create-subfolder-path.png":::
 
@@ -88,13 +89,13 @@ To add an environment definition:
 
 The service scans the repository to find new environment definitions. After you sync the repository, new environment definitions are available to all projects in the dev center.
 
-### Specify a runner for a Terraform custom image
+### Specify a Terraform custom image
 
-The ADE extensibility model enables you to use your own custom container image. You can create and store custom Terraform images in public registries. 
+The ADE's extensibility model enables you to use your own custom container image to deploy your preferred choice of IaC framework. You can even build and leverage your own container image to execute deployments using Terraform. Learn how to [Configure a container image to execute deployments with Terraform](https://aka.ms/deployment-environments/container-image-terraform).
 
-When creating environment definitions that use a custom image in their deployment, the runner property provides a link to a container registry where this container image is stored. 
+When creating environment definitions that use a custom image in their deployment, the runner property provides a link to a container registry where this container image is stored.
 
-The runner property specifies the location of the image you want top use. When you're using a Terraform image and storing it in a public registry, edit the runner property to specify the location that image, as shown in the following example:
+The runner property specifies the location of the image you want to use. When you're using a Terraform image from a container registry, edit the runner property to specify the location that image, as shown in the following example:
 
 ```yaml
 runner: "{YOUR_REGISTRY}.azurecr.io/{YOUR_REPOSITORY}:{YOUR_TAG}"
@@ -106,7 +107,7 @@ You can specify parameters for your environment definitions to allow developers
 
 Parameters are defined in the *environment.yaml* file. 
 
-The following script is an example of an *environment.yaml* file that includes two parameters; `location` and `name`: 
+The following script is an example of an *environment.yaml* file for an ARM template that includes two parameters; `location` and `name`: 
 
 ```YAML
 name: WebApp
@@ -156,13 +157,13 @@ To learn more about the `az devcenter dev environment create` command, see the [
 
 ## Update an environment definition
 
-To modify the configuration of Azure resources in an existing environment definition in Azure Deployment Environments, update the associated ARM template JSON file in the repository. The change is immediately reflected when you create a new environment by using the specific environment definition. The update also is applied when you redeploy an environment associated with that environment definition.
+To modify the configuration of Azure resources in an existing environment definition in Azure Deployment Environments, update the associated template  file in the repository. The change is immediately reflected when you create a new environment by using the specific environment definition. The update also is applied when you redeploy an environment associated with that environment definition.
 
-To update any metadata related to the ARM template, modify *environment.yaml*, and then [update the catalog](how-to-configure-catalog.md#update-a-catalog).
+To update any metadata related to the template, modify *environment.yaml*, and then [update the catalog](how-to-configure-catalog.md#update-a-catalog).
 
 ## Delete an environment definition
 
-To delete an existing environment definition, in the repository, delete the subfolder that contains the ARM template JSON file and the associated environment YAML file. Then, [update the catalog](how-to-configure-catalog.md#update-a-catalog).
+To delete an existing environment definition, in the repository, delete the subfolder that contains the template file and the associated environment YAML file. Then, [update the catalog](how-to-configure-catalog.md#update-a-catalog).
 
 After you delete an environment definition, development teams can no longer use the specific environment definition to deploy a new environment. Update the environment definition reference for any existing environments that use the deleted environment definition. If the reference isn't updated and the environment is redeployed, the deployment fails.
 
