Archive this project

[mjeffryes]

This project introduced a "multi-cloud framework for containers, serverless, and data". It served for many years as a key demonstration of the power of Pulumi's approach of using real programming languages to build Infrastructure as Code. In fact, it was the cornerstone of the examples in Joe Duffy's "Hello, Pulumi!" blog post that first announced the company!

However, as Pulumi has grown over the years, we've slowly moved away from resource model abstractions that span across many clouds for a few reasons:

• Customers who used @pulumi/cloud were broadly not satisfied with it. They frequently ran into the boundaries of the abstractions, and although we did have relatively smooth "falloff" into cloud-specific and lower-level libraries, it wasn't enough to maintain sufficient value in the @pulumi/cloud layer.

• Since this library was built, Kubernetes has taken off as the near universal standard for abstraction across clouds. So there's less demand for alternative cross-cloud abstraction models.

• @pulumi/cloud was designed for application developers - working at meaningfully higher levels of abstraction. In practice, we've found it to be higher leverage to instead focus on serving the platform and core cloud infra teams that support the application developers in their companies. (Similarly, we provide the foundation for other open source app dev focused tools like SST.)

We've retained this repository as a fun example of the history of Pulumi and the versatility of the Pulumi ecosystem. Unfortunately, this means we have not been able to maintain at the level we would like. (The last successful build was 9 months ago.) As a further complication, the name sometimes causes confusion for users who think it is Pulumi Cloud, our managed IaC platform.

Due to all these factors, we've decided it's time to archive this project, so we can keep it as a reminder of our history while continuing to focus on our mission to to bring the power of the cloud to every builder.

Steps

Beta Give feedback

1. Record the context and decision to archive the project in an issue in the repo (Basically a more public facing summary of the context from this document and comments)
2. Update the README file with information about when and why the project was sunset and suggesting some alternatives.
3. Update any blog posts and reference material on pulumi.com to either remove references to the project or add a note about the projects deprecation
4. Update any examples or templates referencing it
5. Close all the open PRs and issues
6. Publish a SDKs with a deprecation notice to package managers
7. Archive the repo