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

Downgraded to 3.118. but pulumi up now Downloading plugin.. So slow via three different VPNs.. These aren't on a CDN?

The plugins are served from GitHub releases, which itself is served via a CDN.  In case users are being rate limited by GitHub releases (or GitHub releases has issues), we do fall back to `<http://get.pulumi.com|get.pulumi.com>` which is served via a CloudFront CDN.

The auto download of "the plugin" (what exactly is it?) was either 243mb or 246mb (cant remember exactly) for 3.118.0 after running `pulumi up` first time on this rolled back version (extract executables from the releases).  I cant see that correlate with anything on <https://github.com/pulumi/pulumi/releases/tag/v3.118.0> - eager to troubleshoot this as this happened a bad time yesterday..

When does it fallback? What are the conditions it would fallback. As workaround for the playbook  I don't mind temporarily poisoning <http://github.com|github.com> in /etc/hosts if it avoids the situation

How do you know a user is being rate limited - is there a header flag in the download from <http://github.com|github.com>?