Originating from a hackathon project, this blog post explores potential solutions to the challenge of resolving circular dependencies in Pulumi programs, a common issue when deploying modern web applications. The text provides a detailed examination of four conceptual solutions: using a "State" object to manage values across deployments, employing "Refs" to integrate dependency tracking into Pulumi's graph, creating "patch" resources to model updates explicitly, and allowing resources to update their goal state dynamically. Each approach is assessed for its feasibility and drawbacks, such as deployment complexity, potential for endless update loops, and increased provider size. While none of the solutions are currently implemented in Pulumi SDKs, the exploration offers valuable insights into managing dependencies and invites further contributions from the community, highlighting the project's open-source nature and ongoing development.