Skip to content

Commit 76ae3cc

Browse files
author
RoseHJM
committed
Generalize custom container image framework references.
1 parent b18486b commit 76ae3cc

File tree

1 file changed

+2
-3
lines changed

1 file changed

+2
-3
lines changed

articles/deployment-environments/configure-environment-definition.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -101,7 +101,7 @@ In the environment.yaml file, the runner property specifies the location of the
101101
|---------------|--------------|
102102
| ARM | ARM |
103103
| Bicep | Bicep |
104-
| Terraform | Not supported |
104+
| Terraform | No sample image. Use a custom container image instead. |
105105

106106
The following example shows a runner that references the sample Bicep container image:
107107
```yaml
@@ -113,14 +113,13 @@ The following example shows a runner that references the sample Bicep container
113113
templatePath: azuredeploy.json
114114
```
115115

116-
### Specify an ARM, Bicep, or Terraform custom container image
116+
### Specify a custom container image
117117

118118
To use a custom container image stored in a repository, use the following runner format in the environment.yaml file:
119119
```yaml
120120
runner: "{YOUR_REGISTRY}.azurecr.io/{YOUR_REPOSITORY}:{YOUR_TAG}”`
121121
```
122122

123-
You should use this runner format whether you're using ARM, Bicep, or Terraform for your custom container image.
124123
Edit the runner value to reference your repository and custom image, as shown in the following example:
125124

126125
```yaml

0 commit comments

Comments
 (0)