Pulumi Reviews & Product Details

I switched to Pulumi in 2019, when I got frustrated with trying to embed any sort of logic into my Terraform configurations. I found Pulumi's approach of using a general purpose programming language made a lot more sense to me. What I like most about Pulumi is that I'm not only solving business problems through infrastructure as code, but I'm also building skill and experience in a programming language. That's transferable and reusable knowledge that adds value to my career. Review collected by and hosted on G2.com.

As someone with an infrastructure/operations background, the learning curve of using a general purpose programming language (I started with TypeScript and later switched to Golang) can be a bit challenging if you don't already know or aren't already familiar with the language. That's not Pulumi's fault; that's just the nature of learning a programming language. The Pulumi documentation needs improvement, but otherwise I haven't run into any issues or problems. Review collected by and hosted on G2.com.

Pulumi is an awesome tool to easily manage Infra-as-code with a new approach more based on code than yaml like its competitors.

Being able to use my favorite langage to manage my infrastructure is really useful.

Onboarding to Pulumi is made easy thank to the complete documentation and a large community to answer any question Review collected by and hosted on G2.com.

What is currently not yet covered at 100% is that some SDKs are not available in all supported langages.

But thanks to the great community it's improving very fast Review collected by and hosted on G2.com.

Allow the TDDers to write automation tests, even IaC code can be tested!

What's more the secret as code is made possible and it's safer than SOPS. (It's harder to make mistakes than with SOPS). Review collected by and hosted on G2.com.

Cognitive load is somewhat higher than expected. Review collected by and hosted on G2.com.

* Pulumi enables us to define our AWS cloud resources through IaC components which is versioned along with our application code.

* For our infrastructure testing requirements, it provides seamless testing, modularization and CI/CD integrations for our deployments.

* Since Pulumi keeps the metadata of our infrastructure, its easy to manage our cloud resources & we make use of its CLI to create/update/delete the stack state.

* There are no security concerns while running commands through its CLI, Pulumi doesn't store any of our cloud credentials. All configurations & secrets are encrypted by our encryption provider. Review collected by and hosted on G2.com.

* We didn't face any inconvenience while using Pulumi as its an open-source IaC platform best suited for our AWS deployments.

* We can easily validate our applications & infrastructure through any native testing frameworks.

* Pulumi Packages promotes reusability of our IaC scripts which saves us a lot of time. Each component is production-ready so we don't have to spend much time on configurations.

* Overall, we are satisfied with the services offered by Pulumi for our cloud infrastructure modularization & deployments. Review collected by and hosted on G2.com.

Pulumi, being the first imperative-based Infrastructure-as-Code tool, has revolutionized the deployment of infrastructure in hyperscalers, making it accessible not only to DevOps engineers but to all engineers. This breakthrough has addressed the challenges faced by DevOps teams, as revealed in the survey conducted by firefly.ai called "State of IaC" (available at https://www.firefly.ai/state-of-iac).

Pulumi (especially Pulumi Cloud) has significantly increased engineering efficiency by streamlining the IaC process, while also simplifying compliance and infrastructure versioning. By reducing the likelihood of downtime or service disruptions, Pulumi aids in troubleshooting infrastructure changes, making it an invaluable asset for organizations striving for optimal performance and reliability. Review collected by and hosted on G2.com.

Migrating from Pulumi Cloud to Pulumi OSS can indeed be a challenging task. Pulumi Cloud offers additional features and capabilities that are not available in Pulumi OSS, which can make the transition more complex Review collected by and hosted on G2.com.

Pulumi allows our team to create IaC projects and allows for project stacks to pull information from each other. This baked-in functionality has been extremely valuable in our hub and spoke architecture, where spokes commonly need to know information about the hub when being provisioned.

Add to that Pulumi's impressive number of supported cloud providers, and the multi-language support for writing code, and we are safe in the knowledge that no matter the cloud provider or language, we'll be able to bring Pulumi along for the ride. Review collected by and hosted on G2.com.

My only dislike of Pulumi is that it's Azure Native Typescript package is too comprehensive. It's a massive library that requires some time to install for developers. As of writing this, a solution is in the works from Pulumi, and I eagerly await it's release. Review collected by and hosted on G2.com.

I love that I can write my IaC to deploy and manage my infra in my perferred programming languages without having to make the mental switch to and from TypeScript to YAML or JSON. It also makes conditional and loops so much easier to write and manage.

Pulumi cloud also provides a great way to visualize your infrastructure stacks across multiple cloud providers without manually viewing each one. Being able to focus on writing code and less on managing infrastructure makes you much more productive. And being able to manage a wide variety of providers is even better. Review collected by and hosted on G2.com.

Pulumi is fairly new in terms of examples and other resources, but the simplicity to get things to work makes up for it. It also requires you to write providers in Golang which I don't have experience in so trying to create a new provider for a cloud platform I want to work with has led to some difficulties, but that's more a me problem. Review collected by and hosted on G2.com.

Pulumi enables for infrastructure code all the quality-of-life improvements that we software developers have come to expect for other code. With it, I have rich IDE support, excellent unit and integration testing capabilities, great static and dynamic analysis, tight integration into build and deployment pipelines, and all the other things that I now consider essential for a satisfactory development experience.

The support (both paid and community-provided) is excellent, the ecosystem of extensions is extensive, and the catalogue of examples is very good (and improving all the time).

Adopting it as a free tool initially means you have to rapidly learn some of the harder concepts; when the tool proves its worth to you and your organization, you naturally move to the paid services and quickly realize how much value they provide across a team and a company. Review collected by and hosted on G2.com.

I've been wracking my brain about this one. I can't think of a dislike that lasted any length of time. There were a few non-obvious learning hurdles along the way, which would have annoyed me as I was working through them, but they've just required a slight shift in thinking or an "a-ha!" moment.

I guess I don't like the implementation of some of the official Pulumi extensions. As an experienced user, I have seen some bits of sugar within their AWSX library in particular that I recommend against using. The base implementation within their classic libraries is no more difficult (albeit a bit more verbose) and avoids some recurring problems that are regularly asked about on the Pulumi community Slack. Review collected by and hosted on G2.com.

Our team has used a number of tools to manage multi-cloud deployments across multiple cloud service providers - Pulumi is hands down the best one out there. It makes working across many different environments a seamless experience not the least because it uses actual programming languages to do so. Because the full power of a programming language (not just templates) is available, full automation is becoming a reality. Iterating through a list of requirements to deploy infrastructure suites is a breeze. Additionally, the additional infrastructure (team collaboration, UI, etc) that Pulumi has built around the toolset really facilitates collaboration at scale. Review collected by and hosted on G2.com.

The templates and examples are terrific and a great place to get started - just wish there were more of them. This is rapidly improving though and the online community is great. Review collected by and hosted on G2.com.

I've been doing overall automation and continuous deployment for over a decade, but it wasn't until I discovered Pulumi that I went all-in for the infrastructure part. As a developer I prefer to use code compared to yaml or something else. I like it because it gives me more trust, if you use a strongly typed version of pulumi like Typescript, and faster feedback since you get answers back directly during compilation.

Having things in code also makes it possible to run "patch jobs" for resources in-process instead of running that code outside the provisioning. Being able to run the "patch job" in-process is excellent for the rare occasions when there might be a missing option in the SDK, which has happened once over three years with the Azure AD provider.

I would argue that most companies need a tool like Pulumi, since the pure cloud tools are limited to just that cloud provider. If you are a larger company, you also want to automate things like Kubernetes, GitHub, Opsgenie and other services out there, and Pulumi has support for a lot of them.

Pulumi automation is another feature we have used to build a self-service application where anyone can "order" different resources through a simple UI and then the application would create them using Pulumi in a compliant manner.

Lastly I would also like to highlight how Pulumi deals with configuration and secrets. How you both store secure configuration in Pulumi and share outputs between different deployments in Pulumi is a killer feature that has simplified a lot of work for us. I often use Pulumi to deal with configuration for more minor things where I'm testing things out since it is much more secure than copying a file. Storing secrets in the Pulumi configuration also makes it very easy to get a new user app running by creating a small script that reads the config and sets appropriate environment variables to get going.

If there is one "infrastructure as code" tool I would recommend, it is Pulumi! Review collected by and hosted on G2.com.

If you are using a cloud tool that isn't well known, the provider for it might be lacking some features, but most users use the more prominent vendors with good coverage. Review collected by and hosted on G2.com.