Hello everyone!
We’re getting started with Pulumi ...
# getting-startedw
witty-finland-45097
10/23/2024, 1:01 PMHello everyone!
We’re getting started with Pulumi and would like to explore the possibility of using a custom configuration file instead of the default pulumi.STACK_NAME.yaml. Our goal is to create a configuration file that can be shared across multiple stacks. Any insights or suggestions on how to achieve this would be greatly appreciated!
FYI: the custom configuration file will reference an esc environment.
Another question regarding the Personal Access token generated in Pulumi Cloud. Is there a way to generate PAT with a scope over a stack/an environment ?
Thank you!
l
little-cartoon-10569
10/23/2024, 6:59 PMConfiguration across stacks is already supported. You can put some configuration in the project config file, Pulumi.yaml. Then just put the parts that are actually different per stack in Pulumi.stack.yaml.
little-cartoon-10569
10/23/2024, 7:00 PMYou don't need to use Pulumi configuration at all if you don't want to: you're using a general-purpose language, so you can do anything. But it's a solved problem, Pulumi does it for you, so the general recommendation is to use the tools that are there.
little-cartoon-10569
10/23/2024, 7:03 PMSeparate questions tend to go best in separate threads. But: Personal Access Tokens are for logging in as a person. If you want to reduce the scope, you can set up a Team with the correct scope and create a Team token for that team. That requires Enterprise licensing.
You could also check the token in code, and allow token X access only stack X, and token Y access stack Y. It's a general purpose language! 🙂
w
witty-finland-45097
10/24/2024, 3:52 PMThank you a lot for your help!