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

This is a known issue.  Update to the latest version and it should work properly :simple_smile: 

I'll stop ignoring that "there's a new version" message, then :stuck_out_tongue:

you could also set the pulumi version update check can be skipped by setting the environment variable PULUMI_SKIP_UPDATE_CHECK to 1 or true if it's bothersome in the future!

here's the issue for reference: <https://github.com/pulumi/pulumi-aws/issues/751>

Although you can skip the update warnings like Dan has shown, personally, I think it is good to be aware of the latest CLI releases. At least then you can consciously ignore a release for a specific reason, than to not know at all that a new release is available. Typically, updating to a new CLI version should be low risk. Like updating to a newer browser version.