Skip to content

Commit e93b3c6

Browse files
authored
Merge pull request #125969 from JFolberth/feature/bicep_parameter_usage
Update parameter-files.md
2 parents f905fae + 172f9f3 commit e93b3c6

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

articles/azure-resource-manager/bicep/parameter-files.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,10 @@ ms.custom: devx-track-bicep
88

99
# Create a parameters file for Bicep deployment
1010

11+
Bicep parameter files allow you to define values in an individual file that are then passed to your `main.bicep` file. The parameter file exposes values that may change from a given subscription, environment, and/or region. Leveraging a parameter file will drive consistency in your IaC deployments while also providing flexibility. Some of this flexibility might allow an organization to take advantage of cost benefits by right-sizing their nonproduction environments while maintaining the same core infrastructure.
12+
13+
These parameter files also help enable a streamlined CI/CD deployment approach. Each parameter file is under source control and passed into the appropriate automated deployment steps. These parameter files ensure a consistent deployment experience.
14+
1115
This article shows you how to create a parameters file, which you can use instead of passing parameters as inline values in your script. You can use either a Bicep parameters file with the `.bicepparam` file extension or a JSON parameters file that contains the parameter value.
1216

1317
> [!NOTE]

0 commit comments

Comments
 (0)