Map Azure DevOps Runtime Variables to Terraform Input Variables

This is a recording of the March 29, 2023 virtual meetup.
The notes for this talk can be found at: github.com/arindam0310018/23-...
In this Session, I will demonstrate -
How to Map Azure DevOps Runtime Variables to Terraform Input Variables.
If at all we need to put the values in variables.tf or in tfvars.
Arindam Mitra
Arindam is an Azure Cloud Solutions & DevOps Architect | Technical Blogger & Speaker Focused on Cloud Adoption, Architecture, Automation, Build and Run in Azure.
Links:
- Blog: dev.to/arindam0310018/
- LinkedIn: / arindam-mitra-28981095
- Twitter: / arindam0310018
- Sessionize: sessionize.com/arindam0310018/
- GitHub: github.com/arindam0310018
- Facebook: / arindam.mitra.790

[@stephenu2352]

*promo sm* 💥

[@user-wq4tw3jz9f]

Great demo and excellent solution to lead terraforming more flexible by having end user input variables, you just provide what I was exactly looking for, Also a quick hint for approval and artifact copy/download steps you may look after below options that more modern with ADO yml pipeline: # Approve - stage: Approve displayName: Approve jobs: - job: approve displayName: Wait for approval pool: server steps: - task: ManualValidation@0 timeoutInMinutes: 60 inputs: notifyUsers: 'your email' instructions: 'Please review the plan in 60 Minutes' and for artifacts: you may use workingDirectory: $(System.DefaultWorkingDirectory) and publishPlanResults: 'Terraform Plan' inputs for each stages rather than copy/download them. Thanks again for the video