azure/vscode-remote-try-bicep

Bicep Authoring Devcontainer

This is a simple devcontainer which can be used with CodeSpaces or VSCode Remote to get all the tooling needed to start authoring bicep.

Quick Start: VSCode Remote

1. Clone the repository.
2. Configure the development environment by installing VSCode and the "Remote - Containers" extension. Quick start docs here.
3. Open the repository in VSCode
4. CTRL+SHIFT+P then type Reopen in container to open the devcontainer in VSCode.
5. Open a terminal in VSCode with CTRL+SHIFT+P -> Terminal: Create new integrated terminal. We'll use this to run Bicep commands.
6. Run az login from the VSCode terminal to connect to your Azure account.
7. Run the following to create a resource group and deploy your Bicep file to it.

   az group create -n my-rg -l eastus
   az deployment group create -f ./main.bicep -g my-rg

8. Open main.bicep in to modify the resources you want to deploy, and re-run the az deployment group command to re-deploy the resources.

Quick Start: Codespaces

1. Open this repository in GitHub Codespaces.
2. Open a terminal in VSCode with CTRL+J. We'll use this to run Bicep commands.
3. Run az login from the VSCode terminal to connect to your Azure account.
4. Run the following to create a resource group and deploy your Bicep file to it.

   az group create -n my-rg -l eastus
   az deployment group create -f ./main.bicep -g my-rg

5. Open main.bicep in your Codespaces window to modify the resources you want to deploy, and re-run the az deployment group command to re-deploy the resources.

Next Steps

Review the Bicep documentation to build out more advanced scenarios.

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.

When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.

vscode-remote-try-bicep's Issues

[Question] microsoft/vscode-dev-containers also has a Developer Container definition

Hi!

Perhaps you are already aware that there is a Developer Container definition for bicep present here: https://github.com/microsoft/vscode-dev-containers/tree/master/containers/azure-bicep

The microsoft/vscode-dev-containers repo is the one that feed VS Code with baked official and community Dev Containers definitions.

To avoid fragmentation shouldn't both definition be merged?

Why is Port 7071 forwarded?

I realize the issue this caused for me is my fault since I just copied and pasted the devcontainer.json without fully comprehending.

However, when this dev container is running, it hijacks the communication of all Azure Function local development (since by default they run on port 7071). Took me a while to realize this was at fault.

I have removed the forwarded port from my devcontainer.json and everything appears to be working fine.

Running Bicep Dev container on VS code failed

Hello,

I ran Bicep Dev container on latest VS code failed,the screenshot is below,any suggestions?

Thanks,
Teo