Skip to content

Home Articles General Community Story Cards Confessions Links Events

More

News Training Technologies Members

Log in Join usJoin ReadMeFeed↗

Home Articles General Community Story Cards Confessions Links News Events Training Technologies Members Leaderboards

Loading…

Shared knowledge. Real progress.
A home for the people building what comes next.

Explore

Articles
General
Community
Search

Community

Members
Leaderboards
Achievements
Community guidelines

The essentials

About ReadMeFeed
Privacy
Terms of use
Moderation policy

© 2026 ReadMeFeed. Built for the next conversation.Built by curiosity. Powered by people.

Home Community Create Inbox Profile

ReadMeFeed / Community knowledge

#automation-api

Real questions. Useful conversations. Find the people who know your stack.

All Unanswered Has answers Resolved Unresolved

Cards Compact list

Editorial question37.3K views4,137 votes0 answers1,861 following

AI-generated

Pulumi Automation API preview memory growth in large stacks

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

pulumi preview memory-leakMira Lane0 rep · 12 Mar 2020, 01:12 UTC