Former software engineer, now in DevOps/Cloud Engineering since 2017. Passionate about the environment, running long distances, backpacking, and veganism. Always seeking sustainable solutions
Thanks for writing this article! I hadn't heard of Bicep before, so I looked it up and discovered that it's another Infrastructure as Code tool used in Azure. If you're familiar with AWS, is this similar to AWS's CloudFormation tool?
It appears that Bicep is being used to create resources for remotely holding the Terraform state and locks. I'd be interested to see how Bicep is run, and it might be helpful to include a discussion about remote state and locks in your article.
I love challenges in terms of programming just to push my limits of coding further, I love to work with new problems, always trying to find logical solutions.
Thanks for the read! Bicep is Azure’s version of Cloudformation. I have used Bicep to spin out storage account and a blob, purpose for doing that was, so i wouldn't need to worry about tfstate for the blob that would manage tfstates for the actual project.
My current bicep code requires a resource group to be created. Then bicep creates the blob inside. After which terraform is ready to take off. 😊
I will update this later on , how my pipelines handle this use case.
Former software engineer, now in DevOps/Cloud Engineering since 2017. Passionate about the environment, running long distances, backpacking, and veganism. Always seeking sustainable solutions
Thanks for writing this article! I hadn't heard of Bicep before, so I looked it up and discovered that it's another Infrastructure as Code tool used in Azure. If you're familiar with AWS, is this similar to AWS's CloudFormation tool?
It appears that Bicep is being used to create resources for remotely holding the Terraform state and locks. I'd be interested to see how Bicep is run, and it might be helpful to include a discussion about remote state and locks in your article.
Thanks for the read! Bicep is Azure’s version of Cloudformation. I have used Bicep to spin out storage account and a blob, purpose for doing that was, so i wouldn't need to worry about tfstate for the blob that would manage tfstates for the actual project.
My current bicep code requires a resource group to be created. Then bicep creates the blob inside. After which terraform is ready to take off. 😊
I will update this later on , how my pipelines handle this use case.
Looking forward to reading it!