A perfectly stable GitHub Actions deployment to Azure SQL suddenly fails with a misleading 'Identity not found' error. Follow the debugging journey to uncover the real culprit that has nothing to do with the identity.
I recently presented "Playing with Azure and Terraform" at our user group locally in Durban, there were some requests for a recording so I thought I'd share it here 😊 We play with a lot of different tech in this session like GitHub Codespaces, Azure, Cloudflare and Snyk
In this video we'll take a look at connecting to Cloudflare with terraform to fully automate a full (strict) SSL/TLS encryption mode setup We'll also cover setting up a basic nginx server which we'll use to validate that our setup is working as expected.
In this video we'll take a look at Managing GitHub secrets using terraform as well as federated identities from GitHub into Azure. You should only be storing secrets if you absolutely need to, in this demo although we are only accessing storage accounts the change from a storage connection string to Azure Federated Identity means that we can access any of resource the identity has access too using RBAC which is a much better overall approach.