Skip to content

Commit 2059549

Browse files
authored
Merge pull request #164493 from mumian/0702-bicep-limits
add Bicep limitations
2 parents e9ca1ff + ab63d0d commit 2059549

File tree

1 file changed

+24
-1
lines changed

1 file changed

+24
-1
lines changed

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

Lines changed: 24 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Bicep language for deploying Azure resources
33
description: Describes the Bicep language for deploying infrastructure to Azure. It provides an improved authoring experience over using JSON to develop templates.
44
ms.topic: conceptual
5-
ms.date: 06/03/2021
5+
ms.date: 07/02/2021
66
---
77

88
# What is Bicep?
@@ -103,6 +103,29 @@ They continue to function exactly as they always have. You don't need to make an
103103

104104
When you're ready, you can [decompile the JSON files to Bicep](./decompile.md).
105105

106+
## Known limitations
107+
108+
- No support for single-line object and arrays. For example, `['a', 'b', 'c']` is not supported. For more information, see [Arrays](/data-types#arrays), [Objects](/data-types#objects).
109+
- No support for breaking long lines into multiple lines. For example:
110+
111+
```bicep
112+
resource sa 'Microsoft.Storage/storageAccounts@2019-06-01' = if (newOrExisting == 'new') {
113+
...
114+
}
115+
```
116+
117+
Can't be written as:
118+
119+
```bicep
120+
resource sa 'Microsoft.Storage/storageAccounts@2019-06-01' =
121+
if (newOrExisting == 'new') {
122+
...
123+
}
124+
```
125+
126+
- No support for the concept of apiProfile which is used to map a single apiProfile to a set apiVersion for each resource type.
127+
- No support for user-defined functions (UDFs).
128+
106129
## Next steps
107130
108131
Get started with the [Quickstart](./quickstart-create-bicep-use-visual-studio-code.md).

0 commit comments

Comments
 (0)