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

CleanShot 2023-11-06 at 16.25.23@2x.png

ok, i got somewhere. when using an s3 backend, it places the Pulumi.yaml and stack yaml file in a temporary folder, where the node modules of pulumi is not available

<@U01BRSYUUDP> is this Automation API with an inline program using a dynamic provider?

<@U01BRSYUUDP> if you say it works with our cloud backend, is it only the `backend` property that you remove from the `projectSettings`?

Is this with fresh stack state for both filestate and service?

yes, a clean run in a bull queue worker for a new stack

```      try {
        currentStack = await LocalWorkspace.selectStack({
          stackName,
          workDir: this.isDevelopmentMode ? `/tmp/${process.env['NAMESPACE'] || process.env['USER']}` : '/data',
        });
        await currentStack.cancel();
      } catch (error) {
        // swallow the error: stack does not exist
      }

      const stack = await LocalWorkspace.createOrSelectStack(
        {
          stackName,
          projectName: `bpaas`,
          program: async () =&gt; {
            return await pulumiProgram();
          },
        },
...```

is it possible that the workdir for selectStack bleeds through to createOrSelectStack?

it is supposed to error out in step 1, and then create a new one

I don't think so, but if the dynamic resources already exist in the stack selected the dynamic provider might not even be getting started up

I strongly suspect your service stack already has data, and thats why it _appears_ to work

i did try those cases, but i also have it on new stacks

That's very odd then. I can't see anything backend specific in the startup code :confused:

yeah, stook me a wile to get it going, but by forcing the workdir to the calling dir it works just fine