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
The extensibility model enables platform engineers to define the app infrastructure using their preferred IaC framework including Azure Resource Manager (ARM), Bicep, Terraform, and Pulumi. Platform engineers create and customize container images for different scenarios. They push these images to a container registry and reference them in the environment definition’s metadata file. This ensures that whenever a deployment is made, the deployment execution happens based on how the container image is configured. The following diagram shows the relationship between the custom images stored in a container registry, and the environment definition within the catalog.
21
+
The extensibility model enables platform engineers to define the app infrastructure using their preferred IaC framework including Azure Resource Manager (ARM), Bicep, Terraform, and Pulumi. Platform engineers create and customize container images for different scenarios. They push these images to a container registry and reference them in the environment definition's metadata file. This ensures that whenever a deployment is made, the deployment execution happens based on how the container image is configured. The following diagram shows the relationship between the custom images stored in a container registry, and the environment definition within the catalog.
@@ -52,13 +52,13 @@ For instructions, see: [Create a custom container image manually](https://aka.ms
52
52
53
53
To make the process of building a custom image and pushing it to a container registry easier, Microsoft provides a script that builds and pushes the image to a registry that you specify.
54
54
55
-
For instructions, see: [Create a custom container image by using a script](https://aka.ms/ade/arm-bicep-custom-script).
55
+
For instructions, see: [Create a custom container image by using a script](https://aka.ms/ade/terraform-custom-script).
56
56
57
57
**Create a custom image using a GitHub workflow**
58
58
59
-
To make the process of building a custom image and pushing it to a container registry easier, Microsoft provides a script that builds and pushes the image to a registry that you specify.
59
+
To make the process of building a Terraform-based image and pushing it to a container registry easier, you can use a published workflow that builds and pushes the image to a registry that you specify.
60
60
61
-
For instructions, see: [Create a custom container image by using a script](https://aka.ms/ade/arm-bicep-custom-script).
61
+
For instructions, see: [Create a custom container image by using a script](https://aka.ms/ade/terraform-workflow).
62
62
63
63
**Create a Terraform specific container image manually**
@@ -168,7 +168,7 @@ Run the workflow by navigating to the Actions tab in your forked repository and
168
168
169
169
To use the image in your environment deployments, you need to add the location of the image to your manifest file [Connect the image to your environment definition](#connect-the-image-to-your-environment-definition) and you might need to configure permissions for the ACR to [make the custom image available to ADE](#make-the-custom-image-available-to-ade).
170
170
171
-
### [Create an image using a script](#tab/terraform-manual/)
171
+
### [Create an image manually](#tab/terraform-manual/)
0 commit comments