This message was deleted.

sparse-intern-71089

03/27/2021, 6:39 AM

This message was deleted.

better-shampoo-48884

03/27/2021, 8:14 AM

One hint seems to be that automation overwrote my existing Pulumi.yaml.. that's not right is it? Same name + runtime, but lost the description, config and backend stuff

better-shampoo-48884

03/27/2021, 9:50 AM

Yup - that was it - turns out that my declaration of Pulumi.yaml would be overwritten entirely and disregarded by automation, so if I wanted to use it, I had to import it myself:

const currentProject = yaml.load(fs.readFileSync("./Pulumi.yaml"))

and the LocalWorkspace:

..projectSettings: currentProject..

better-shampoo-48884

03/27/2021, 9:51 AM

Still getting the error code 4294967295 though - and I have a feeling it might be due to my absolutely massive stack output.. it contains all the stack resources and all the configuration elements used to create it, including temporary configuration operations to create the final result..

better-shampoo-48884

03/27/2021, 9:52 AM

I.e. my design decision at the moment is - it doesn't hurt to just throw it in the output 😄.. Guess I might be wrong

lemon-agent-27707

03/27/2021, 3:40 PM

You should not need to do this. If you just set

workDir

to the directory that contains your pulumi yaml, it will pick it up automatically.

better-shampoo-48884

03/27/2021, 4:29 PM

well - it didn't. it overwrote the already existing Pulumi.yaml, even when i did not have any

projectSettings

defined.

lemon-agent-27707

03/28/2021, 4:48 PM

If you specified

workDir

without explicit

projectSettings

then this behavior would be a bug and we should fix it. If you have a repro, please share or file an issue: https://github.com/pulumi/pulumi/issues/new?assignees=&labels=kind%2Fbug&template=0-bug-report.md

better-shampoo-48884

03/29/2021, 12:42 PM

Bug raised: https://github.com/pulumi/pulumi/issues/6632 Includes link to repo for reproduction.

39 Views

Open in Slack

Previous Next

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.