https://pulumi.com
Join Slack
This message was deleted.
# general
s
This message was deleted.
m
I don't believe so because of the tight coupling with the 
pulumi config
command, even in the automation API. https://github.com/pulumi/pulumi/blob/master/sdk/nodejs/automation/localWorkspace.ts#L416
which has that annoying side effect of removing your YAML file when you 
pulumi stack rm
a
Yeah, I kind of wish stacks were more internal than the 
.yaml
that ends up functioning as config.
There's a design choice somewhere inside of how stacks and stack configs work that make them difficult to reuse between projects.
I don't know if this is the right way to put it, but it's almost like I wish "stack state supported multiple projects".
m
Yes, I ran into this issue when trying to abuse Config for my own needs, not a stack. I had manage my own YAML separately 😞 (first world cloud development problems)
a
Yeah, and now I find myself writing shell scripts to manage this away as I don't want to be managing multiple files all with the same base settings.
I think I've got a strategy for it, but it's just obviously weird.
The symlinking to the 
.yaml
file helps me keep just one config file with config for all my projects in it.
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