search

Azure / caf-terraform-landingzones

This solution, offered by the Open-Source community, will no longer receive contributions from Microsoft. Customers are encouraged to transition to Microsoft Azure Verified Modules for continued support and updates from Microsoft. Please note, this repository is scheduled for decommissioning and will be removed on July 1, 2025.
https://github.com/aztfmod/caf-terraform-landingzones
MIT License
761 stars 666 forks source link

[Discussion/Thought] Multi-tenant / cross-org / partner deployments #107

Open XavierGeerinck opened 4 years ago

XavierGeerinck commented 4 years ago

Hi all!

Thanks for this amazing contribution, this makes it super clear on how to manage large projects as well as to define what should be in place at which levels to make it manageable for the different people / groups working on a project within an organization.

From a partner side of view, I am currently working on a "Service Offering" catalog, where I am looking to have some kind of "lego" blocks that can be taken and shaped together for deployment on a customer their subscription (think a button that a customer can click and it automatically deploys). Focusing on the following points:

Now, while working with this project, it seems that certain things are made more complex than they should be (personal opinion). Giving the reason why I opened this issue. Would it be possible to share your opinion around the following?

Kind Regards, Xavier Geerinck

arnaudlh commented 4 years ago

hi Xavier, maybe this will help a little bit to answer some of your questions, I will come back later on the others:

LaurentLesle commented 3 years ago

@XavierGeerinck we are adding support for Multi-Tenant-Multi-Subscription scenarios in the June release. This should support the scenario you are describing.