Try creating a new project using pulumi.com, and a new project using local state. Do they both work?

I have another container based on the same image for another project working just fine still

don’t you know any way to get some better debug trace from the

pulumi

program ? it is usually pretty good at telling what’s wrong when there’s a problem.

I can confirm that’s a code (module/plugin ?) related issue, even locally this project does not work, even going back to old commits that worked before obviously (and purging

node_modules

to ensure the same context) while another project has no problem doing an update, crossing out a backend issue. Doesn’t really makes sense. I’ll try to investigate further, but a better debug log would really help.

You could try

-v=3

or

-v=9

, but it the exception is being throw so early, even that might not help..

@billowy-army-68599 I’m up to date I think,

2.18.2

I’ve finally got the situation back to normal. It seems it was because of a version discrepancy on

@pulumi/aws

between a module I use requiring it and the main project (the module was requiring

3.23.0

while the project was

^3.20.0

which resulted on using the last one (

3.25.1

). After forcing the main project to

3.23.0

like the module dependency, I got

pulumi up

to work again. I hate node modules. Thanks for having taken the time to help guys