From 82c5e5431edb163e807d5f72bdbe282c24e7ca20 Mon Sep 17 00:00:00 2001 From: Erika Gressi Date: Sat, 9 Jul 2022 20:02:21 +0200 Subject: [PATCH 1/3] update interoperability --- docs/wiki/Interoperability - Bicep to ARM conversion.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/docs/wiki/Interoperability - Bicep to ARM conversion.md b/docs/wiki/Interoperability - Bicep to ARM conversion.md index d0931acf53..b20d227c7e 100644 --- a/docs/wiki/Interoperability - Bicep to ARM conversion.md +++ b/docs/wiki/Interoperability - Bicep to ARM conversion.md @@ -1,6 +1,10 @@ -Bicep is a relatively new Domain-specific language (DSL) and - at the time of writing - not yet in the state of General Availability (GA). For this reason, some people may want to wait for Bicep's _General Availability_ and prefer to use ARM/JSON for the time being. + +Bicep is [ready for production use](https://docs.microsoft.com/en-us/azure/azure-resource-manager/bicep/frequently-asked-questions#is-this-ready-for-production-use) starting with version 0.3. It is supported by Microsoft support plans and has parity with what can be accomplished with ARM Templates. + +However, Bicep is a relatively new Domain-specific language (DSL) and - at the time of writing - not yet in version 1.0. For this reason, some users may want to wait before adopting Bicep in their environment and prefer to use ARM/JSON for the time being. For these scenarios, the CARML library provides a script that uses the Bicep Toolkit translator/compiler to support the conversion of CARML Bicep modules to ARM/JSON Templates. + This page documents the conversion utility and how to use it. --- From bf31ed947e11362d2c266723b1ae69ffd6a0f0d9 Mon Sep 17 00:00:00 2001 From: Erika Gressi Date: Sat, 9 Jul 2022 20:05:06 +0200 Subject: [PATCH 2/3] arm json --- docs/wiki/Interoperability.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/wiki/Interoperability.md b/docs/wiki/Interoperability.md index e0718df833..c7cf78cc00 100644 --- a/docs/wiki/Interoperability.md +++ b/docs/wiki/Interoperability.md @@ -1,6 +1,6 @@ -This section explores how CARML can work with both Bicep & ARM JSON templates, as well as GitHub Actions & Azure DevOps Pipelines to meet different customer scenarios. +This section explores how CARML can work with both Bicep & ARM/JSON templates, as well as GitHub Actions & Azure DevOps Pipelines to meet different customer scenarios. -This is how you will run different scripts and set up a module in either ARM JSON Template or Bicep syntax and configure a CI/CD pipeline using Azure DevOps or GitHub. +This is how you will run different scripts and set up a module in either ARM/JSON Template or Bicep syntax and configure a CI/CD pipeline using Azure DevOps or GitHub. --- From 0108e7c6e8c04386df560d32b2e538186536cb5f Mon Sep 17 00:00:00 2001 From: Erika Gressi Date: Mon, 11 Jul 2022 13:03:58 +0200 Subject: [PATCH 3/3] remove reasons for using arm over bicep --- docs/wiki/Interoperability - Bicep to ARM conversion.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/docs/wiki/Interoperability - Bicep to ARM conversion.md b/docs/wiki/Interoperability - Bicep to ARM conversion.md index b20d227c7e..9ef44cdf4b 100644 --- a/docs/wiki/Interoperability - Bicep to ARM conversion.md +++ b/docs/wiki/Interoperability - Bicep to ARM conversion.md @@ -1,9 +1,7 @@ Bicep is [ready for production use](https://docs.microsoft.com/en-us/azure/azure-resource-manager/bicep/frequently-asked-questions#is-this-ready-for-production-use) starting with version 0.3. It is supported by Microsoft support plans and has parity with what can be accomplished with ARM Templates. -However, Bicep is a relatively new Domain-specific language (DSL) and - at the time of writing - not yet in version 1.0. For this reason, some users may want to wait before adopting Bicep in their environment and prefer to use ARM/JSON for the time being. - -For these scenarios, the CARML library provides a script that uses the Bicep Toolkit translator/compiler to support the conversion of CARML Bicep modules to ARM/JSON Templates. +However, for users who still prefer using ARM templates over Bicep, the CARML library provides a script that uses the Bicep Toolkit translator/compiler to support the conversion of CARML Bicep modules to ARM/JSON Templates. This page documents the conversion utility and how to use it.