User Profile
j_folberth
Joined 4 years ago
User Widgets
Recent Discussions
Re: Azure DevOps Org Patterns for separated teams
For the YAML I think you are looking for Templates in a shared repository. This repository could be stored in a seperate project. Based on what you are saying above I'd recommend a call to the centralized template in a repository gated by those with the appropriate access. (personally, would call a stage template which would call a job template which would call a task template). The template should accept the "project name". This project name should ultimately also be part of a variable template which is also in the central repository and under appropriate permissions. The variable template based on the project will contain the specific information such as the source connection and other pieces. I have a series of blogs that outlines some of the practices: https://techcommunity.microsoft.com/t5/healthcare-and-life-sciences/bg-p/HealthcareAndLifeSciencesBlog/label-name/YAML%20Pipeline%20Series Hopefully this helps.1KViews1like0CommentsRe: Azure DevOps Org Patterns for separated teams
It still is not clear when referring to "infra in one project'" is this a single repo w/ all the infrastructure or a repo per app infrastructure? There is a way to chain pipelines together; however, I feel this will cause overhead and run some risk as a good practice is typically have a single multi-stage pipeline that goes to DEV, STG, then PRD as opposed to three separate pipelines with one for each environment. I THINK what you would be looking at is something like a YAML repository resource block that will copy the source infrastructure from the repository and produce it as an artifact to the development team's pipelines. This will limit their control/ability to update the Infra; however, have a copy associated with their app code pipeline and deployed with it. This will really help if ever needing to rollback and prevent any environment drift. To achieve this in the developer pipeline the IaC project/repository would be declared as a resource block https://learn.microsoft.com/en-us/azure/devops/pipelines/process/resources?view=azure-devops&tabs=schema#define-a-pipelines-resource Then will want to publish the IaC to the developer pipeline https://learn.microsoft.com/en-us/azure/devops/pipelines/artifacts/pipeline-artifacts?view=azure-devops&tabs=yaml This will also have the benefit of consolidating pipelines and ensuring the IaC components are deployed via a Service Connection. The developers will still not be able to maintain the IaC; however, have the ability to control deployment of it. Alternatively, since you are in ARM/Bicep would recommend at least evaluating the use of Bicep Registries https://learn.microsoft.com/en-us/azure/azure-resource-manager/bicep/private-module-registry?tabs=azure-powershell to centralize your templates for mass consumption.1.3KViews0likes3CommentsRe: Azure DevOps Org Patterns for separated teams
Would need to know more detail to better answer this question. When we say central IaC pipeline are referring to a central repository or a pipeline that deploys an entire subscription(s) resources? Also is this around a module based deployment (Bicep, ARM, Terraform?)1.3KViews0likes5Comments
Recent Blog Articles
Azure DevOps Pipelines: Discovering the Ideal Service Connection Strategy
Embarking on the journey of deploying code into Azure through Azure DevOps brings forth a crucial question: how should your DevOps environment communicate with your Azure resources? In this in-depth ...6.2KViews3likes0CommentsPart 5 - Unlock the Power of Azure Data Factory: A Guide to Boosting Your Data Ingestion Process
Leveraging Linked ARM Templates for your Azure Data Factory deployments? Not a problem as this article will outline the steps to successfully build and deploy your linked ARM templates for Data Facto...6.2KViews1like0Comments