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

I do not believe it should be updated frequently, but it is possible.  You're saying when you see failures you have to log in again from the CLI because it prompts you to do so?

yeah it does, I get the promp even though i have credentials set in my `~/.pulumi/credentials.json`

Okay, I believe what is going on here is basically the same root cause as this issue: <https://github.com/pulumi/pulumi/issues/1202>

When the CLI starts up, we test to see if you are logged in so we can prompt you eagerly.  I am guessing that check fails and we don't distinguish DNS resolution error vs <http://pulumi.com|pulumi.com> said your token was incorrect.