Importing Private Terraform Modules

[@Wahlnetwork]

Today we step into a more complex Terraform deployment using private modules and continuous integration (CI) to construct foundational resources in an AWS region. This is a fairly popular workflow across any cloud provider as it builds out all of the networking and security resources needed by future applications. Private modules allow you and your team to build opinionated blocks of code that can be used across numerous infrastructure as code (IaC) projects.

[@petrar2d2]

Nooo don't give up, such great videos. You are trying to help out in a helpful manner.. you explain intimidating stuff in such a clear and honest way. Please, comeee back 😄😄

[@ezrablack5395]

I can't thank you enough for the way you explained each step of your code. This video was extremely helpful!!

[@phuletravinh4912]

thank you so much for these videos, I can hear so clearly and simple English from you, easy understand for me

[@Dynamic_reelz]

Amazing lecture🏆

[@joshhazlecood2556]

Awesome video Chris!

[@vighneshpp]

Amazing Video. Subscribed!!

[@andresf-v8x]

great job dude

[@mum0l57]

Good job, thanks!

[@Oswee]

How do you deal with // repository beeing sourced multiple times into the project? I mean... if you use // syntax 20 times then entire "private-modules" repository is cloned 20 times into the project .terraform directory. Also... how do you deal with cases where some older app project is put in the maintenance mode and needs to have older "private-module" version? In all the docs and talks HashiCorp is pretty against "monorepo" (//) setup. At first it feels appealing, easy DX, etc. But as you have more and more projects, module versioning becomes the bottleneck. Primary projects works with full CI/CD from the main branch, but some projects needs to have older shared module version. As it seems to me right now... one module per repository in long term is way to go. Yes, management is bit hard and clumzy... imagine like 100 modules and 100 repositories... :) But... until Git does not allow some kind sub-tags for the repo directories... it's the most future proof way to manage modules. IMO.

[@vishalkalal]

Great video Chris. I have one question, what will happen when you would use Checkov or any security tools? I tried checkov but fails to download the private repo to analyze the code.

[@VishwanathYadwad]

As like you mentioned source url I also done same thing but getting access denied. How to pass git credentials here. If possible tell how can we make of gitlab module registry here.

[@BrothersGame77]

I like your eyes, then your videos :)

[@carlosrodolfoschradergarci2159]

Hi chris this video is just awesome, thanks for sharing this private module aproach is very usefull, i have some experience with terraform but i cant fully comprenhend why on the gateway configuration your vpc_id is var.parent_aws_vpc_id instead of aws_vpc.name_of_the_vpc.id ?, by the way i would love if you could make a terraform course on Udemy, Thanks a lot

[@Wahlnetwork]

Howdy! In this scenario, the VPC is being created by the "vpc-transit" module. The VPC id value is returned from that module using an output and then passed to the "transit-gateway" module. I use the term parent to help my brain understand that the information is coming from somewhere else. Thanks for the kudos!

[@carlosrodolfoschradergarci2159]

@@Wahlnetwork Thanks a lot, as im new using parent and child modules i did not notice it, but i have seen your other videos and now i can comprenhend it, really thanks a lot men you are the best !

[@GauravKamdar-i2j]

Great videos. Please lose the background music!! or reduce the volume. It gets hard to focus on the real content.

[@johnmorsley]

Please, please, please, lose the background music. I literally cannot watch! :"(