Pulumi Community

This message was deleted.

s

Slackbot

over 3 years ago

This message was deleted.

s

j

+2

4
12
150

I recently upgraded to Pulumi v3.122.0, and now `pulumi up` fails on one of my stacks with the error...

r

Roy Keene

12 months ago

I recently upgraded to Pulumi v3.122.0, and now

pulumi up

fails on one of my stacks with the error:

error: Error: ENOENT: no such file or directory, stat '<stackname>'
        at Object.statSync (node:fs:1690:3)
        at resolveConfigPath (/home/rkeene/devel/project/node_modules/tsconfig-paths/src/tsconfig-loader.ts:90:9)
        at loadSyncDefault (/home/rkeene/devel/project/node_modules/tsconfig-paths/src/tsconfig-loader.ts:60:12)
        at tsConfigLoader (/home/rkeene/devel/project/node_modules/tsconfig-paths/src/tsconfig-loader.ts:47:20)
        at configLoader (/home/rkeene/devel/project/node_modules/tsconfig-paths/src/config-loader.ts:66:22)
        at Object.register (/home/rkeene/devel/project/node_modules/tsconfig-paths/src/register.ts:80:25)
        at Object.<anonymous> (/home/rkeene/devel/project/node_modules/tsconfig-paths/register.js:1:15)
        at Module._compile (node:internal/modules/cjs/loader:1256:14)
        at Module._extensions..js (node:internal/modules/cjs/loader:1310:10)
        at Object.require.extensions.<computed> [as .js] (/home/rkeene/devel/project/node_modules/ts-node/src/index.ts:1608:43)

It's not clear why it cares that there is no directory named