Pulumi Upgrade Failure: No Automatic Rollback for Provider Plugins

When executing pulumi upgrade, the CLI downloads and installs provider plugins into the local .pulumi/cache directory. If the process aborts mid-download or a plugin fails to initialize, the stack may remain in a failed state while the new plugin files persist in the cache.

The current recovery workflow requires manual intervention: uninstalling the failed plugin version, reinstalling the previous stable version, and running pulumi refresh. There is currently no native CLI flag, such as --rollback, to automate the reversion of provider changes upon an error.

This lack of automated recovery creates a risk of state inconsistency where subsequent upgrade attempts fail due to stale or mismatched plugin files in the local environment.

• Is there a specific command or configuration to atomically revert provider plugin changes if an upgrade fails halfway?
• What is the safest method to clear the .pulumi/cache to prevent stale plugin files from interfering with manual recovery efforts?
• Is there a documented roadmap for a built-in rollback mechanism to handle provider-level upgrade failures?