Skip to content

[Wiki] Fix incorrect statement about Bicep not being GA #1657

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
eriqua merged 3 commits into from
Jul 11, 2022
Merged

[Wiki] Fix incorrect statement about Bicep not being GA #1657

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
82c5e54
update interoperability
eriqua Jul 9, 2022
bf31ed9
arm json
eriqua Jul 9, 2022
0108e7c
remove reasons for using arm over bicep
eriqua Jul 11, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions docs/wiki/Interoperability - Bicep to ARM conversion.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,8 @@
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.

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.
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, 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.

---
Expand Down
4 changes: 2 additions & 2 deletions docs/wiki/Interoperability.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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.

---

Expand Down