Channels
pulumi-ai
package-authoring
pulumi-cdk
oracle-cloud-infrastructure
learn-pulumi-events
linen
registry
built-with-pulumi
pulumi-cloud
contribex
testingtesting321
hacktoberfest
cloudengineering
yaml
pulumi-crosscode
content-share
finops
multi-language-hackathon
office-hours
workshops
blog-posts
localstack
welcome
gitlab
pulumi-kubernetes-operator
jobs
aws
pulumi-deployments
dotnet
golang
announcements
java
pulumiverse
python
install
getting-started
cloudengineering-support
testingtesting123
hackathon-03-19-2020
typescript
google-cloud
contribute
azure
kubernetes
docs
automation-api
status
general
Title
l
lively-controller-39972
02/05/2023, 1:36 PMHi everyone. I have a "production" branch, a "staging" branch and then multiple feature branches. Should I create a stack per branch in my CI?
o
orange-policeman-59119
02/05/2023, 3:48 PMDefinitely. You will want a stack per branch so that the resources deployed in each are separate from one another.
l
lively-controller-39972
02/05/2023, 3:49 PMSo for each, I need to create Pulumi.[branch-name].yml with my config?
It doesn't seem very optimal because I am just going to copy paste the same config everytime
m
miniature-musician-31262
02/05/2023, 5:52 PMYou might want to check out project-level configuration, which can help reduce some of this kind of duplication: https://www.pulumi.com/blog/project-config-mvp/
l
lively-controller-39972
02/05/2023, 9:45 PMProject level conf is conf that applies to all stacks, so that is not what is appropriate in the situation?
o
orange-policeman-59119
02/05/2023, 10:15 PMIt doesn't seem very optimal because I am just going to copy paste the same config everytime
Project level config will allow you to put the common configuration in Pulumi.yaml, and the unique config that is per-stack in each of the separate stack config files.
l
lively-controller-39972
02/05/2023, 11:46 PMYes, but what if I want to deploy my stack
feature-brancho
orange-policeman-59119
02/05/2023, 11:47 PMUse the CLI or automation API to configure your per-branch stacks. Use project config for common configuration.
If you have constants that are the same across all of your stacks, you can put those in code as well, if it makes more sense.
n
nutritious-beach-57252
02/06/2023, 5:37 AMn
narrow-guitar-10891
02/06/2023, 8:04 AMYou can create one Pulumi.default.yaml (for example) and on feature branches run:
pulumi up --stack ${BRANCH_NAME_SLUG} --config-file Pulumi.default.yamll
lively-controller-39972
02/06/2023, 12:30 PMThanks @narrow-guitar-10891for your solution!! That seems to be the correct way of handling my problem!
n
narrow-guitar-10891
02/06/2023, 12:30 PM🔥