Azure DevOps Fireside Chats is an opportunity to talk with DevOps professionals about a different subject every month. In February we discussed Infrastructure as Code (IaC). IaC helps codify your IT solutions allowing you to specify everything you need in a declarative manner.

Watch a conversation between April Edwards, Jay Gordon, Steven Murawski, and Puppet Labs Eric Sorenson as they try to answer questions on IaC from the Azure Community.

2:50 – Introductions
14:39 – What are the benefits of Project Bicep over Azure Resource Manager templates?
22:00 – What strategy is best for engaging people to use IaC?
24:49 – How do you handle organizations that are hostile to change?
32:10 – At what size project should you start using IaC?
37:32 – If your cloud stack is Azure, which tool is the best for IaC?
48:18 – Is it appropriate for IaC to be part of the main repo, or a separate one?

The Microsoft Docs definition of IaC by Sam Guckenheimer:

Infrastructure as Code (IaC) is the management of infrastructure (networks, virtual machines, load balancers, and connection topology) in a descriptive model, using the same versioning as DevOps team uses for source code. Like the principle that the same source code generates the same binary, an IaC model generates the same environment every time it is applied. IaC is a key DevOps practice and is used in conjunction with continuous delivery.

Let’s reduce the manual work and use these tools, whether Terraform, ARM, or even your Kubernetes manifest.

March 2021 Edition: Agile Development

Our next session will be held on March 17th, 2021 where Abel Wang and Damian Brady will help give us a look into Agile Development with moderator Jay Gordon. We need your questions!

Want to know more about team dynamics in Agile? How does Agile differ from DevOps? How do we get started?

Go to this form and submit your burning questions on Agile Development.

We’ll see you on March 17th, 2021 at 4PM PST / 7PM EST on LearnTV!