ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
DevOps & observability · #pulumi
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
Memory retention during repeated preview invocations The Pulumi Automation API runs the engine in‑process and keeps the full resource state graph alive for the lifetime of a Workspace . When repeatedly creating a stack, previewing, and disposing the workspace, users observe a steady increase in resident memory that does not plateau, even after calling worksp