https://pulumi.com
Join Slack
This message was deleted.
# general
s
This message was deleted.
o
Definitely. You will want a stack per branch so that the resources deployed in each are separate from one another.
l
So 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
You 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
Project level conf is conf that applies to all stacks, so that is not what is appropriate in the situation?
o
It 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
Yes, but what if I want to deploy my stack 
feature-branch
for each of my feature branch? How could I do?
o
Use 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
n
You can create one Pulumi.default.yaml (for example) and on feature branches run: 
pulumi up --stack ${BRANCH_NAME_SLUG} --config-file Pulumi.default.yaml
🙌 2
l
Thanks @narrow-guitar-10891for your solution!! That seems to be the correct way of handling my problem!
n
🔥
3 Views
Open in Slack
PreviousNext
Powered by

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Powered by