This message was deleted.
# automation-api
s
This message was deleted.
b
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
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..
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..
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
l
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.
b
well - it didn't. it overwrote the already existing Pulumi.yaml, even when i did not have any
projectSettings
defined.
l
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
b
Bug raised: https://github.com/pulumi/pulumi/issues/6632 Includes link to repo for reproduction.