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

The fix we found it to manually modify the JSON file to our username, then it works o_o

We can make the manual fix or run a `pulumi up` beforehand via automation API which modifies the state files accordingly

From my best debugging efforts, we are sure that `pulumi` is properly configured with the `SNOWFLAKE_USER` etc.

However, when the sql connection to snowflake is opened, `pulumi` seems to be attempting to use the resource metadata (aforementioned json) to initiate the connection rather than what is configured.

We believe this has only started happening recently so I'm taking a look at the recent changes for dependencies that `pulumi` has to provide snowflake IaC capabilities.

upon further investigation, modifying the json directly is a terrible idea and leads to interesting side effects.

`up` is the only solution we have for it but that makes no sense for when we are trying to run `destroy`