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
Copy file name to clipboardExpand all lines: articles/azure-resource-manager/bicep/bicep-config.md
+11-3Lines changed: 11 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: Bicep config file
3
3
description: Describes the configuration file for your Bicep deployments
4
4
ms.topic: conceptual
5
-
ms.date: 01/18/2023
5
+
ms.date: 02/18/2023
6
6
---
7
7
8
8
# Configure your Bicep environment
@@ -11,7 +11,7 @@ Bicep supports a configuration file named `bicepconfig.json`. Within this file,
11
11
12
12
To customize values, create this file in the directory where you store Bicep files. You can add `bicepconfig.json` files in multiple directories. The configuration file closest to the Bicep file in the directory hierarchy is used.
13
13
14
-
## Create the config file in VSCode
14
+
## Create the config file in Visual Studio Code
15
15
16
16
You can use any text editor to create the config file.
17
17
@@ -38,12 +38,20 @@ The following sample enables the [user-defined types in Bicep](https://aka.ms/bi
38
38
```json
39
39
{
40
40
"experimentalFeaturesEnabled": {
41
-
"imports": true,
42
41
"userDefineTypes": true
43
42
}
44
43
}
45
44
```
46
45
46
+
The available experimental features include:
47
+
48
+
-**extensibility**: Allows Bicep to use a provider model to deploy non-ARM resources. Currently, we only support a Kubernetes provider.
49
+
-**paramsFiles**: Allows for the use of a Bicep-style parameters file with a terser syntax than the JSON equivalent parameters file. Currently, you also need a special build of Bicep to enable this feature, so is it inaccessible to most users. See [Parameters - first release](https://github.com/Azure/bicep/issues/9567).
50
+
-**sourceMapping**: Enables basic source mapping to map an error location returned in the ARM template layer back to the relevant location in the Bicep file.
51
+
-**resourceTypedParamsAndOutputs**: Enables the type for a parameter or output to be of type resource to make it easier to pass resource references between modules. This feature is only partially implemented. See [Simplifying resource referencing](https://github.com/azure/bicep/issues/2245).
52
+
-**symbolicNameCodegen**: Allows the ARM template layer to use a new schema to represent resources as an object dictionary rather than an array of objects. This feature improves the semantic equivalent of the Bicep and ARM templates, resulting in more reliable code generation. Enabling this feature has no effect on the Bicep layer's functionality.
53
+
-**userDefinedTypes**: Allows you to define your own custom types for parameters. See [User-defined types in Bicep](https://aka.ms/bicepCustomTypes).
54
+
47
55
## Next steps
48
56
49
57
-[Add module settings in Bicep config](bicep-config-modules.md)
0 commit comments