During this week's bridge update rollout, several PRs failed with a 502 Bad Gateway on installing the pulumi cli. This is unlikely to be unique to bridge updates, although it's possible to be related to a "bulk" upgrade on all providers.
See more failed runs under "Merged After Rerun due to a 502 on install-pulumi-cli" in the tracking issue.
Do we still need to explicitly install the pulumi CLI? The main benefit that I see is that we would be guaranteed the latest CLI every time. How far behind is the pulumi version available on github runners?
During this week's bridge update rollout, several PRs failed with a 502 Bad Gateway on installing the pulumi cli. This is unlikely to be unique to bridge updates, although it's possible to be related to a "bulk" upgrade on all providers.
See more failed runs under "Merged After Rerun due to a 502 on install-pulumi-cli" in the tracking issue.
Do we still need to explicitly install the pulumi CLI? The main benefit that I see is that we would be guaranteed the latest CLI every time. How far behind is the pulumi version available on github runners?