Skip to content

Commit 2b56123

Browse files
committed
add a list of experimental features
1 parent ae49802 commit 2b56123

File tree

1 file changed

+10
-2
lines changed

1 file changed

+10
-2
lines changed

articles/azure-resource-manager/bicep/bicep-config.md

Lines changed: 10 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Bicep config file
33
description: Describes the configuration file for your Bicep deployments
44
ms.topic: conceptual
5-
ms.date: 01/18/2023
5+
ms.date: 02/17/2023
66
---
77

88
# Configure your Bicep environment
@@ -38,12 +38,20 @@ The following sample enables the [user-defined types in Bicep](https://aka.ms/bi
3838
```json
3939
{
4040
"experimentalFeaturesEnabled": {
41-
"imports": true,
4241
"userDefineTypes": true
4342
}
4443
}
4544
```
4645

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 inaccessbile to the majority of 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**: Enable this feature to use a new schema in the ARM template layer to represent resources as an object dictionary instead of an array of objects. This makes the Bicep and ARM template more semantically equivalent and leads to more reliable code generation. Enabling this does not result in any functionality changes in the Bicep layer.
53+
- **userDefinedTypes**: Define your own custom types for parameters. See [User-defined types in Bicep](https://aka.ms/bicepCustomTypes).
54+
4755
## Next steps
4856

4957
- [Add module settings in Bicep config](bicep-config-modules.md)

0 commit comments

Comments
 (0)