In part 2 we learned how to lint our powershell, and automate unit testing using Github actions. In this third and final part, we’ll talk about automating your module release using GitHub Actions as well as generating a static documentation site.

Infrastructure as Code isn’t a new concept, but is one a lot of folks are missing out on. I’m a huge believer that cloud resources should be in a stable and predictable state. Using tools such as Terraform, Azure ARM templates, or any other IaC provider creates that predictable state. I’m going to talk a little about why it’s important, and my opinion on how to best implement it.

In part 1 we focused on getting our PowerShell validated using Unit Tests and Code Coverage. The second part of this series will focus on using a CI/CD service to automate the process and linting your code with PSScriptAnalyzer.

PowerShell is getting a lot of buzz since PowerShell 7 was released. A tried and true friend to Windows SysAdmins, now stable and available for most Linux distributions. PowerShell is a very robust tool to create automation that makes your life easier. But, with any software, we need predicatbility when releasing these tools.