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

Basically I want the inverse, ambient_plugins_are_ok, be quiet about it :smile:

For now ignoring the ambient things seems to remove the warning, does seem a bit weird though.

This is probably a little different in Nix, but for most users, in the general case you want to use the plugins that pulumi installed itself. They’d be in `~/.pulumi/plugins/` or similar, which is not on the PATH, but pulumi knows to look there.

When a plugin is found on the path, that means - outside of Nix - that it was manually downloaded or copied. That can cause unintended behavior.

`PULUMI_IGNORE_AMBIENT_PLUGINS` tells Pulumi to ignore these plugins on the PATH.

I see, that aligns more or less with my predictions. As the versions are locked in pulumi-land, I'm fine with using the env var. The warning was just a little non-actionable :slightly_smiling_face:

Thanks for clarifying!