You now have Azure Verified modules for both terraform and bicep which is essentially git sub modules but they're maintained by Microsoft and individual contributors which also sit in the TF registry when using TF. Feels like an evolution of whats shown in this video but possibly simpler and ive found them much easier to nest in modules etc.
great advance modular approach and clean structure TF coding:) would you please provide more examples at the repo provisioning a vm and vent-peering along with security group assignment and windows vm extensions?
I was partly on this path with my refactoring. However I keep asking myself if I’m digging a hole by doing simple wrappers around terraform resources. Eg. Module for a resource group Seems like it goes against what Hashicorp recommends. Don’t create simple wrappers Ok any case, I’ve got about 20 or so modules created following this pattern and not looking back. I find the locals files are getting long in some cases with app gateways and apps etc.
>However I keep asking myself if I’m digging a hole by doing simple wrappers around terraform resources. Eg. Module for a resource group Yes, it is a bad practice.
This is really great, is there a repo available? What version is this available on? I also wonder how this would work with existing infrastructure and having to pull those into a state file (reverse terraforming)?
I like the modular approach however given through what I've been through the last 5 years, I am highly discouraging the use of git submodules as it creates a lot of complexity when it comes down to versioning and management within medium/large teams
Example with for loops in locals (not for_each) when speaker convert one structure to another are worth to see. But all other stuff... Well, at least that combo of bad practices works fine for him.
You now have Azure Verified modules for both terraform and bicep which is essentially git sub modules but they're maintained by Microsoft and individual contributors which also sit in the TF registry when using TF. Feels like an evolution of whats shown in this video but possibly simpler and ive found them much easier to nest in modules etc.
great advance modular approach and clean structure TF coding:) would you please provide more examples at the repo provisioning a vm and vent-peering along with security group assignment and windows vm extensions?
I was partly on this path with my refactoring.
However I keep asking myself if I’m digging a hole by doing simple wrappers around terraform resources. Eg. Module for a resource group
Seems like it goes against what Hashicorp recommends. Don’t create simple wrappers
Ok any case, I’ve got about 20 or so modules created following this pattern and not looking back.
I find the locals files are getting long in some cases with app gateways and apps etc.
>However I keep asking myself if I’m digging a hole by doing simple wrappers around terraform resources. Eg. Module for a resource group
Yes, it is a bad practice.
This is really great, is there a repo available? What version is this available on? I also wonder how this would work with existing infrastructure and having to pull those into a state file (reverse terraforming)?
I like the modular approach however given through what I've been through the last 5 years, I am highly discouraging the use of git submodules as it creates a lot of complexity when it comes down to versioning and management within medium/large teams
Life saver
Example with for loops in locals (not for_each) when speaker convert one structure to another are worth to see.
But all other stuff... Well, at least that combo of bad practices works fine for him.
git submodules?? are you kidding me?? worst best practice ever!
nothing here is advanced it is normal