Skip to content

Commit 10d48da

Browse files
authored
Update parameter-files.md
Provided overview on when to use parameter files.
1 parent 20b2fd5 commit 10d48da

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 files exposes values which may change from a given subscription, environment, and/or region. Leveraging a parameter file will drive consistency in your IaC deployments while also providing flexability. Some of this flexability may allow an organization to take advantage of cost benefits by right sizing their non production environments while maintaining the same core infrastructure.
12+
13+
These parameter files also help enable a streamline 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)