here Hello everyone My team me basically has been tasked to

Question

here Hello everyone My team me basically has been tasked to deploy Azure infra using Pulumi I understand that I need to do something like a console app that will list the resources that we need APIM AKS etc etc On my terminal I can play with some basic commands to try to deploy infra and then destroy My plan is to keep the pulumi c code on a different repo KYC Pulumi My question is around the integration with Azure Devops I ve found several articles that explain how to preview build and deploy However the Pupumi repo will list all infra components that I might not need for a given API For example I want to deploy only an App Service with Cosmos or AKS setup with SQL etc etc My point is that I want to selectively deploy and not deploy all components listed in my pulumi repo How do I control that ANy ref

stocky-restaurant-98004 · Answer

I m not sure what you mean list all infra components Pulumi is declarative so if you `new` something up it will create it or change if necessary If something is in Pulumi state and it s not longer in your Pulumi program it will delete it

stocky-restaurant-98004 · Answer

If you re referring to `ComponentResource`s I recommend you hold off on using them until you re very comfortable with the basics

fierce-dinner-64337 · Answer

I need to get comfortable soon

fierce-dinner-64337 · Answer

Let le rephrase

fierce-dinner-64337 · Answer

the pulumi console project will be responsible to provision azure stack api management cosmos sql aks bla bla

fierce-dinner-64337 · Answer

When we do smtg like pulumi up it will create whatever we have on that dll right

stocky-restaurant-98004 · Answer

Correct whatever you `new` up Pulumi will manage its lifecycle

fierce-dinner-64337 · Answer

what if want to select what we create from that dll

stocky-restaurant-98004 · Answer

For example

fierce-dinner-64337 · Answer

Imagine that this pulumi console repo will be referenced by an x number of API s that will have different needs

fierce-dinner-64337 · Answer

for instance API A will need App services and SQL but API B will only need AKS and Cosmos so I don t want to deploy all components that are listed on my pulumi dll s

fierce-dinner-64337 · Answer

an example is the terraform modules

stocky-restaurant-98004 · Answer

Make a separate Pulumi program for each API

fierce-dinner-64337 · Answer

is that the best way

stocky-restaurant-98004 · Answer

The analogy of a TF module in Pulumi is a ComponentResource but I recommend you skip them for now until you are sure you need them

fierce-dinner-64337 · Answer

this is not a department with 5 engineers

stocky-restaurant-98004 · Answer

You can refactor to ComponentResources once you have something up and running

fierce-dinner-64337 · Answer

there will be various teams that they will want to reference pulumi dll s but nobody wants to maintain 100 pulumi projects

stocky-restaurant-98004 · Answer

What s the first deliverable that you need to deliver

fierce-dinner-64337 · Answer

I have 2 weeks to set up infra infra includes resource groups AKS KeyVault APIM Redis They want to do a Poc and then make it official but the mandate is pulumi They are 100 sure I

fierce-dinner-64337 · Answer

they use Azure DevOps

fierce-dinner-64337 · Answer

I don t mind the tool I think its great its the deadline that make me freak out

stocky-restaurant-98004 · Answer

If you want to make a shared infra component library that can sometimes be helpful but at the same time making an abstraction before you re ready can cause more pain the long run Especially with infrastructure where breaking changes can be non starters like you can t take down the prod DB or have a virtual network get re created

stocky-restaurant-98004 · Answer

How many app teams do you need to create infra for

fierce-dinner-64337 · Answer

Our customers are those teams We have 5

stocky-restaurant-98004 · Answer

5 teams 5 separate Pulumi programs should be manageable

stocky-restaurant-98004 · Answer

Refactor to ComponentResource if necessary but copy paste is not always bad You have to really write a few programs to make sure that a ComponentResource is useful that it s actually abstracting something

fierce-dinner-64337 · Answer

ok so 5 executables for now and then refactor if I need to

stocky-restaurant-98004 · Answer

Unless there are shared components like an AKS cluster or something

stocky-restaurant-98004 · Answer

If there s shared stuff like everything is deployed into the same virtual network then put that in its own stack and add whatever stack outputs you need so the app teams can deploy into those shared resources

stocky-restaurant-98004 · Answer

But the key thing IMO is to get one team up and running end to end before you do any refactoring Start with that

fierce-dinner-64337 · Answer

Yes I understand Thanks Josh

stocky-restaurant-98004 · Answer

No problem and good luck

fierce-dinner-64337 · Answer

Pulumi weekend

stocky-restaurant-98004 · Answer

FYI you can also define Azure DevOps resources with Pulumi There s an ADO provider

fierce-dinner-64337 · Answer

I found this among others <https build5nines com beginners guide to pulumi ci cd pipelines >

stocky-restaurant-98004 · Answer

Defining pipelines in code has been very helpful for me in the past If all the pipelines are the same and just differ by the source repo THAT would be a good place to try a ComponentResource When you re ready to try them keep them in the same repo as they are used Publishing them to NuGet can be helpful but it comes with considerable maintenance overhead

stocky-restaurant-98004 · Answer

But first things first I recommend you try to get one team s infra working end to end from your machine then maybe move on to creating a pipeline

fierce-dinner-64337 · Answer

yes Thanks for taking time to answer my questions

stocky-restaurant-98004 · Answer

My pleasure Check this out as well <https www pulumi com docs guides continuous delivery azure devops >

fierce-dinner-64337 · Answer

+1