Great content and explanation. Could you please also create content for multiple account with IAM STS Assume Role for provisioning resources in other AWS accounts. This is my suggestion for other viewers to increase the playback speed. Goto settings -> playback speed -> 1.75
If you will create backend.conf file for each env and it is working but here my question is instead of creating this backend.conf and passing it like dev.tfvars so why we will not do these things by creating workspace for each env ? Because in workspace no need to pass in command line because each workspace has its separate statefile
Its very much informative video
Terraform advance series complete playlist ruclips.net/video/v3M_PJAcpzU/видео.html
Great content and explanation. Could you please also create content for multiple account with IAM STS Assume Role for provisioning resources in other AWS accounts. This is my suggestion for other viewers to increase the playback speed. Goto settings -> playback speed -> 1.75
Love your explanation
26:14 terragrunt.
With terragrunt, everything is very easy... the blast radius is very low.
please share complete training video thanks.
If you will create backend.conf file for each env and it is working but here my question is instead of creating this backend.conf and passing it like dev.tfvars so why we will not do these things by creating workspace for each env ? Because in workspace no need to pass in command line because each workspace has its separate statefile
Nice explaination
Well explained,but since we created 2 different backend with backend.config,is there any need for workspace?
yes there a need since in same aws account you may want to configure multiple workspaces like - dev, stage, etc.
why you do not use terragrunt ?
Thank you so much