Feature: DMLZ outputs in deploying DLZ via DevOps #229
-
Feature or Idea - What?The "params.*.json" files seem to only include fixed values in the many IDs asked, could these be re-written as variables that use the actual outputs from the DMLZ that has been deployed earlier? Or how does this all work with Azure DevOps pipelines? I pasted two sample parameters: The outputs set in the end of "main.json" can be found in Azure deployment history, yet the DLZ script doesn't seem to request those and instead uses the fixed values from the "params.*.json" file, which does not seem too automated? Or am I not seeing something? Feature or Idea - Why?We have a repo deploying the DMLZ and then we need those outputs in all the possible future DLZ deployments that are located in another repo, how can those be linked even after time has passed? Code of Conduct
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 5 replies
-
Thanks @Hurvester for the question! We are seeing that these two artifacts (Data Landing Zone and Data Management Landing Zone) usually have a different lifecycle and are also often managed by separate teams. Hence, they will land in different repositories on the customer side and will be deployed individually. There is the possibility to merge the data landing zone and data management landing zone artifacts and deployments into one repository and CI/CD pipeline, if both of them have the same lifecycle on your side and if both of them are managed by the same team. However, even if this is the case today, I would not advise to do that. The responsibilities and ownership may also change over time or may change for a subset of Landing Zones. Separating the two artifacts later would be more tedious than just keeping them separate right from the beginning. However, in general merging the two IaC artifacts is indeed possible and the proper outputs are already defined so that they can be passed between the two IaC templates. In fact, this is setup because we are already doing this for the All-in-one deployment that you can find here: https://github.com/Azure/data-management-zone/blob/main/docs/reference/dataManagementAnalytics.bicep Please let me know if more clarity is required. If this answer was helpful and answers all your questions, then please flag this answer (Mark as answer). |
Beta Was this translation helpful? Give feedback.
Thanks @Hurvester for the question!
We are seeing that these two artifacts (Data Landing Zone and Data Management Landing Zone) usually have a different lifecycle and are also often managed by separate teams. Hence, they will land in different repositories on the customer side and will be deployed individually.
There is the possibility to merge the data landing zone and data management landing zone artifacts and deployments into one repository and CI/CD pipeline, if both of them have the same lifecycle on your side and if both of them are managed by the same team. However, even if this is the case today, I would not advise to do that. The responsibilities and ownership may also change ove…