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.

Pulumi Community

related issue: <https://github.com/pulumi/pulumi/issues/423>

I think you're using automation API though, right? IIRC. So you may want to checkout the code, specifically the `LocalWorkspace` constructor as that is where it decides when it should write to those files. I believe if you provide `projectSettings` or `stackSettings` it will do an overwrite.

well, using both. This in particular was the CLI part - i'll convert it over to automation when it's a bit more stable :slightly_smiling_face: happy to use automation for kubernetes at the moment, but not for critical baseline infra worth literally millions of dollars a month to us  :slightly_smiling_face:

(which is also why I'm hoping that my using pulumi to manage this might convince them to consider actually ponying up for it :smile: )

for automation I tend to be 100% decalarative anyway, any files are temporary and not to be trusted. worst case, if I can't do that, I'll persist them in json format in mongo or something, or just push them back and forth to a blob.