-
Notifications
You must be signed in to change notification settings - Fork 667
[question] CAF Terraform landing zones Project direction #520
Comments
The company I work for is having exactly same questions. There is also terraform-azurerm-caf-enterprise-scale and terraform-azurerm-lz-vending that partially overlap with each other and caf-terraform-landingzones. There is no guidance on which module to use for specific use cases. We want to migrate to vWAN, and I have a choice to bring it up with one of these 3 modules, but which one is the right one to use for this requirement? And which modules are still supported by Microsoft, and which will be supported long term? |
Our company are also facing similar challenges - we were an early adopter to the CAF TF landingzones and are now in a situation where it is not supported by MS but the Azure Verified Modules are not mature enough to transitioning to! The AVMs sound good on paper but are they going to be another open-source project by MS that they lose interest in and leave invested customers hanging! Also, Bicep appears to be getting more update love than TF within the AVM's! |
Revisiting Azure CAF from a couple of years ago, and I see that the original Repos are no longer supported. The front-page readme now points to one of the old projects in the Getting Started section.
The link for 'platform starter repository' is now an archived repo. Therefore I would assume that the Any sort of clean-up or updated docs on how to start and which repo is for what would be very appreciated. Edit: Note that https://github.com/Azure/caf-terraform-landingzones/tree/main/caf_solution has broken links too |
Hi not sure where to ask this so I thought I'd raise an issue in the repo.
The linking in the documentation for CAF/SRE Azure SRE Doco is a little confusing as some links/videos no longer work.
Is this cat-terraform-langingzones repo and the rover repo no longer MS supported? Or is the Rover repo no longer MS supported, but this CAF-Terraform-landingzones repo is?
If I go to Terraform registry page for aztfmod caf super module and then to the git repo for the caf super module there is the update that this is no longer MS supported.
So does that mean that as this repo, leverages the super module repo that the landing zone repo is supported but there isn't support for the underpinning supermodule (other than community updates)?
Is this repo going to align with this new azure verified modules? Will the supermodule just become made up of azure verified modules? Or would the plan be to sunset this service and instead have one of the other landing zone repos or something else?
Why is there so many different types of terraform landing zone repos in the azure project they all seem pretty similar in their objective?
Am I completely wrong in my assessment here (It is completely possible I am totally on the wrong track).
Thanks in advanced
Lewis
The text was updated successfully, but these errors were encountered: