This message was deleted.

sparse-intern-71089

10/26/2023, 5:09 AM

This message was deleted.

dry-keyboard-94795

10/26/2023, 6:22 AM

Running

pulumi about

should give details on dependencies. 4.5.0 was yanked (release removed), updating to 4.5.1 should fix the plugin

dry-keyboard-94795

10/26/2023, 6:31 AM

You've mentioned 2 ways of managing python dependencies here, requirements.txt and pyproject.toml. Which are you trying to use to run pulumi?

fresh-orange-37907

10/26/2023, 8:15 AM

Looks like delete the whole venv and do

pip install requirements.txt

do the trick. But am I doing this right? I feel like I lock myself to one plugin version. Because if I ever to update the plugin version. It’ll replace everything on my cluster. Are there any best practice doing this?

dry-keyboard-94795

10/26/2023, 8:18 AM

My understanding of the issue is that it's the preview being over-cautious. To play it safe, you can do

pulumi up --target 'provider urn'; pulumi refresh

dry-keyboard-94795

10/26/2023, 8:18 AM

It's a known issue, something on Pulumi's radar

fresh-orange-37907

10/26/2023, 8:21 AM

Thank you very much, I’ll try this. Is there an issue about this on github that I could follow?

dry-keyboard-94795

10/26/2023, 8:41 AM

https://github.com/pulumi/pulumi-kubernetes/issues/2370

❤️ 1

Open in Slack

Previous Next

Pulumi Community

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.