Infrastructure automation is a must in order to save time and bring efficiency to your organization, and in order to achieve that we use a plethora of tools/scripts however who validates what has been written is production proof or not? The DevOps who wrote the code does that on its own? This has been the ideal practice. However, in this course, we would take you through the principles of Testing in the Infrastructure world and make you aware of how you could get your infrastructure tested before deploying on production.
We would start with the fundamentals of Infrastructure testing; we will try to learn from a few of the recent examples where security breaches could have been avoided if there were proper security/infra testing in place.
We would then move on to learning about an open-source testing tool called Inspec by a company called chef where we would write a bunch of tests in ruby, iterating through our resources on Azure like storage account, and key vault. We would also automate the entire process by integrating the variables with Terraform output.
In the third module we would kick start testing in Golang with the help of a tool called Terratest which is a Go library that provides patterns and helper functions for testing infrastructure, with 1st-class support for Terraform, Packer, Docker, Kubernetes, AWS, GCP, and more, in this section we would start from scratch writing out the first test for Azure resources using Golang.
And by the end we would understand how monitoring in the cloud is different from conventional monitoring set up on-premises, we will also learn about using APIs to automate alerts.
