Leverage from Pester to automate Azure Storage Account testing
summary
Uses Pester with the Az PowerShell module, Terraform and GitHub Actions to run automated validation against Azure Storage Accounts: creates Key Vault secrets and service principal auth, generates SAS tokens, provisions two customers × three environments (six deployments), iterates ~12 storage accounts and runs 54 tests in one run. Tests actually upload and download a file, verify SAS and service principal access, check TLS version and https-only, enforce key rotation and add then remove runner IP with ~30s propagation; the pipeline works and surfaces real failures.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:08Pester and Azure Storage
- 4:40Manual testing challenges
- 9:37Network access and CI/CD
- 19:19Demo setup and Azure CLI auth
- 24:37Pester basics and test example
- 30:35Single storage access test
- 36:54All customer storage tests
- 41:26Policy validation and token checks
- 44:32Conclusion and key takeaways
related talks
35mIaC Automated Assurance
58mWho tests their cloud code anyway?
17mDeep dive on Azure Load Testing in CI/CD
46mAutomating Infrastructure as Code with Azure DevOps
45mGitHub Actions for Fun and Profit
42mYour Microsoft 365 test automation framework
43mBeyond Pester 102: Acceptance testing with PowerShell
40mTest Before You Deploy; How to Test Your ARM Deployments