Add a new Pulumi Cloud, What Is It, topic page #14185
Conversation
|
Your site preview for commit 53b189b is ready! 🎉 http://www-testing-pulumi-docs-origin-pr-14185-53b189b6.s3-website.us-west-2.amazonaws.com. |
|
Aside @aaronkao I do think a few screenshots could go a long way. And maybe that table I had in the appendix in the Google Doc. Or perhaps they'd just distract -- I had a similar conundrum when adding links. What do you think? Worth the effort? |
There was a problem hiding this comment.
It overall seems fine.
I think it would be good to pair it with this grid I started to work on that walks through all the steps to DIY and the equivalent action done in PCloud. Its all broken up by jobs to be done and categorized by value/benefit.
|
|
||
| ## In Summary | ||
|
|
||
| Pulumi Cloud helps teams adopt collaborative, secure, and robust cloud engineering practices. Pulumi's infrastructure as code tool is [open source](https://github.com/pulumi), and by default it leverages Pulumi Cloud to make adopting IaC in your team easier, secure, and reliable out-of-the-box. |
There was a problem hiding this comment.
I don't think the definition of Pulumi Cloud in the first sentence is clear. I think we should answer with Pulumi Cloud is...
There was a problem hiding this comment.
Pulumi Cloud is a fully managed infrastructure management platform that covers three products...
probably some of the stuff in the 3rd paragraph can be moved into this paragraph
|
|
||
| So you've chosen to use Pulumi infrastructure as code, and are now deciding how to manage your state and whether Pulumi Cloud is a good fit? Or you've heard Pulumi is open source but aren't entirely clear on what part is fully open and free, and what is a paid Pulumi product? This page will give you a better understanding about the answers to these questions and everything in between. | ||
|
|
||
| ## In Summary |
There was a problem hiding this comment.
Just dropping my intro for my 2nd rev of PCloud vs DIY blog post here in case you want to steal from it...
Many companies are building internal developer platforms or modern infrastructure platforms to provide developer self-service while maintaining security and compliance. Companies adopt Pulumi IaC so they can apply software engineering to their infrastructure scaling problems and because it is fully open source with a strong community and public roadmap.
At Pulumi, we’re committed to open source—always have been, always will be. Our Pulumi IaC is entirely open source (Apache 2.0 license), meaning you can adopt and extend it however you like. If you’re new to Pulumi, the open source edition is an excellent way to start modernizing your infrastructure. But as your organization grows and the complexity of your environment increases, you may find yourself devoting significant time to rolling your own enterprise IaC backend features. That’s why we built Pulumi Cloud—to help you avoid building and maintaining these capabilities from scratch while ensuring you can automate, secure, and manage your infrastructure at scale.
Pulumi Cloud provides enterprise capabilities that make it easier to automate, secure, and manage these modern infrastructure platforms. However, not every organization has an immediate need for the enterprise features in Pulumi Cloud. Companies receive increasing value from Pulumi Cloud as their organization and their infrastructure platforms grow in size and complexity.
|
|
||
| The first thing you will notice with Pulumi Cloud is that all of your [projects, stacks, and resources](/docs/pulumi-cloud/projects-and-stacks/) are easy to see, search, and explore. A complete history of who has changed what, when, and how -- with full resource change diffs and links both into the source changes that triggered a deployment as well as forward links to the resources in your cloud consoles -- is always present. | ||
|
|
||
| All actions taken by teammates on Pulumi Cloud are logged for [full auditability](/docs/pulumi-cloud/admin/audit-logs/). Full deployment logs are also captured and easy to review to facilitate debugging failures. This is particularly useful for unattended deployments as is common with the [Pulumi Automation API](/automation) and [Pulumi Kubernetes Operator](/docs/iac/using-pulumi/continuous-delivery/pulumi-kubernetes-operator/). All deployment history for all time is maintained and organized. |
There was a problem hiding this comment.
unattended sounds like something went rogue
maybe "non-human deployments" sorta like how there is "non-human identities (NIH)" in the security space, meaning aka machines or agents
|
|
||
| Pulumi's projects and stacks model facilitates collaboration especially thanks to the IaC tool's configuration model, but Pulumi Cloud goes beyond this by offering Pulumi ESC, a way to define so-called environments that group together configuration and secrets that frequently version together. This enables Don't Repeat Yourself (DRY) practices so that you can secure access to cloud accounts, share sensitive information, and deliberately roll out changes to them, across many groups of projects and stacks that are related to each other. | ||
|
|
||
| Pulumi Cloud also offers short-lived stacks in the form of [Review Stacks](/docs/pulumi-cloud/deployments/review-stacks/) -- ephemeral environments stood up just for the duration of a Pull Request, making verification of changes much more robust and seamless -- as well as [Time-to-Live (TTL) Stacks](/docs/pulumi-cloud/deployments/ttl/), which ensure that temporary stacks get automatically cleaned up, enabling more productive engineering workflows without the risk of cloud waste. |
There was a problem hiding this comment.
TTL sorta doesn't fit into this section on Collaboration. It almost feels like it should be part of a Cost Savings or Operations
There was a problem hiding this comment.
Most of the customers who use TTL tell me they would not be comfortable giving their developers direct access to spin up stacks, to use features like review stacks, etc, without it, all of which are basically about collaboration. I have not heard many folks talking about "cost savings" other than this specific point.
|
|
||
| Pulumi Cloud is the easiest way to adopt Pulumi's open source IaC tool at scale, securely, reliably, and collaboratively. | ||
|
|
||
| That said, DIY backends are fully supported and this article's goal is to ensure you can make an educated decision about what is better suited for your use case. The[state and backends topic](/docs/iac/concepts/state-and-backends/) describes in-depth how Pulumi IaC uses Pulumi Cloud and DIY backends and other architectural considerations. |
There was a problem hiding this comment.
| That said, DIY backends are fully supported and this article's goal is to ensure you can make an educated decision about what is better suited for your use case. The[state and backends topic](/docs/iac/concepts/state-and-backends/) describes in-depth how Pulumi IaC uses Pulumi Cloud and DIY backends and other architectural considerations. | |
| That said, DIY backends are fully supported and this article's goal is to ensure you can make an educated decision about what is better suited for your use case. The [state and backends topic](/docs/iac/concepts/state-and-backends/) describes in-depth how Pulumi IaC uses Pulumi Cloud and DIY backends and other architectural considerations. |
|
Your site preview for commit a865188 is ready! 🎉 http://www-testing-pulumi-docs-origin-pr-14185-a8651882.s3-website.us-west-2.amazonaws.com. |
Co-authored-by: Troy Howard <[email protected]> Co-authored-by: aaronkao <[email protected]>
|
Your site preview for commit 4acae62 is ready! 🎉 http://www-testing-pulumi-docs-origin-pr-14185-4acae623.s3-website.us-west-2.amazonaws.com. |
|
Your site preview for commit 9ffced6 is ready! 🎉 http://www-testing-pulumi-docs-origin-pr-14185-9ffced67.s3-website.us-west-2.amazonaws.com. |
No description provided.