Excellent content. You guys earned a subscriber. My only suggestion is to make that screen share a bit clearer, or high def. The video of the primary presenter is crystal clear, but the screen share is a bit fuzzy.
Thanks for the comment! I recently shared detailed pictures from that video to our Discord subscribers to help with this one, but I'll check into ensuring we're capturing higher resolution screen shares too.
In one way, TF always duplicates modules locally when you run *init*. The reason you might exercise changes on that module is just out of simplicity. Terraform will reference the local module until you run an init again (forced if necessary). I found in my time working with large systems it was helpful to work out problems in your initialized Terraform instance while still progressing work, and then moving my changes back into the modules git repo after I had validated my work. In my case, the sub-modules are actually stored in a separate repo from the Terraform root module so that they can be version controlled separately.
![[TH] VALORANT Champions Seoul - Grand Final - EDG vs TH](http://i.ytimg.com/vi/WvObMc9VelI/mqdefault.jpg)
Thanks for sharing your deep knowledge on Terraform! Finally a video where it's not just covering the surface level of Terraform.
Well illustrated and explained; makes perfect sense. Two thumbs up!
Thanks, Mei! Such an honor to have you aboard!
a true gem
This is an incredible video guys, for some reason I always have a hard time wrapping my mind around this as someone not from a heavy Dev background.
Excellent content. You guys earned a subscriber. My only suggestion is to make that screen share a bit clearer, or high def. The video of the primary presenter is crystal clear, but the screen share is a bit fuzzy.
Thanks for the comment! I recently shared detailed pictures from that video to our Discord subscribers to help with this one, but I'll check into ensuring we're capturing higher resolution screen shares too.
At around 14:30, why duplicate a module into a 'local' modules folder? Maybe just branch the modules repo. KISS, DRY
In one way, TF always duplicates modules locally when you run *init*. The reason you might exercise changes on that module is just out of simplicity. Terraform will reference the local module until you run an init again (forced if necessary). I found in my time working with large systems it was helpful to work out problems in your initialized Terraform instance while still progressing work, and then moving my changes back into the modules git repo after I had validated my work. In my case, the sub-modules are actually stored in a separate repo from the Terraform root module so that they can be version controlled separately.
What is the diagramming tool you were using?
It's a mind mapping tool - XMind