Summary

In this chapter, we reviewed how to set up the Bicep extension in VS Code to create a powerful and efficient developer environment that helps you get started with Bicep using a rich authoring experience. Then, we saw how we can configure the Bicep linter to leverage its power and make the authoring experience even better by finding warnings and errors using the Bicep configuration files. You learned how to configure different rules with different levels and make sure your Bicep files are adhering to coding standards that are used by the developer community and other organizations.

You also got to know Azure Bicep Playground, which helps you compile your Bicep files into ARM templates, decompile your ARM templates to see the resulting Bicep file, and take advantage of hundreds of sample templates created by the community to become familiar with Bicep, without the need to install any tool on your local environment.

In the next chapter, we will cover compiling and decompiling...