
We've used Pulumi as our IaC tool of choice for several years. The programmatic way you can interact with your infrastructure provides a powerful interface for modularizing infrastructure components. This allows our organization to develop standardized shared libraries in Python that other stacks can import and use to deploy secure, repeatable, and scalable infrastructure without needing to re-invent the wheel each time or rely on copying and pasting long code segments between projects. This in turn reduces errors and time spent focused on resolving security vulnerabilities. We're able to fix it once, centrally, and then pulumi up our dependent stacks in order to resolve the security issues.
Pulumi is a great product overall. It offers a wide range of cool features that make infrastructure-as-code (IaC) development easier and more efficient. One of the strongest aspects of Pulumi is its support for native programming languages like Python, Node, Jave, Yaml Go, .net. This allows developers to leverage their existing skills and use familiar tools to define and manage infrastructure resources. What I really appreciate about Pulumi is that you don't have to be a full-time developer to understand and work with it. As someone from a systems engineering background, I found it straightforward to pick up and start using as my preferred IaC platform. Pulumi's documentation and community resources are also very helpful. They provide clear and concise guidance, making it easier to get started and troubleshoot any issues that may arise. One notable advantage of Pulumi is its ability to simplify the creation of cross-account and cross-region resources within a single stack. This means you can define and manage resources that span multiple AWS accounts or different regions without the need for complex configuration or external tools like Terraform and Terragrunt. Overall, I have had a positive experience with Pulumi and it has become my go-to choice for infrastructure provisioning and management. Its support for multiple programming languages, ease of use, and strong feature set make it a powerful tool for anyone involved in IaC development.
Empowering Infrastructure as Code with Unmatched Simplicity and Flexibility We have been using Pulumi for quite some time now and I must say, a game-changer in the world of Infrastructure as Code (IaC), has seamlessly blended simplicity with unparalleled flexibility, revolutionizing the way developers and devops manage and deploy infrastructure. As a dedicated user, I am thrilled to share my insights into the remarkable advantages and features that make Pulumi stand out in the crowded landscape of IaC solutions 1) Multi-Cloud Magic 2) Programming Language Freedom: 3) Live Updates and Preview: 4) Reusable Components with Pulumi Packages 5) Granular Resource Management Features: 1) Infrastructure as Code (IaC) 2.0 Pulumi heralds the next generation of IaC, transforming it into a more dynamic, expressive, and collaborative practice. With Pulumi, your infrastructure code is not just static definitions but a living, breathing part of your development workflow. 2) State-of-the-Art Providers: Pulumi's extensive library of providers covers a wide spectrum of services, ensuring that you can model, deploy, and manage a diverse set of cloud resources effortlessly. 3) Secure and Compliant: With built-in support for industry-standard compliance frameworks and best practices, Pulumi ensures that your infrastructure deployments are not just agile but also meet the highest security standards.
We are avid users of Pulumi at VirtusLab because it's the first devops tool that really gives the steering wheel back into the hands of developers. It allows us to take ownership of critical parts of systems we build and helps us to deliver value fast and correctly. A must use for any large infrastructural project. Highly recommended.
With excellent customer support, and a veritable Swiss army knife of cloud providers and languages to choose from to write your IaC, Pulumi has our back, and we are confident we'll take them with us, wherever we go.
I've been using Pulumi for a while now, and I can't help but be amazed at how it has transformed my infrastructure deployment and management workflows. Unlike other IaC tools that rely on domain-specific languages, Pulumi leverages real programming constructs. This makes it feel more natural for developers and reduces the learning curve
Pulumi is my favourite infrastructure as code tool. The ability to write IaC using real programming languages is a game changer and adds so much flexibility to how I deploy infrastructure. Things like the automation API and Pulumi deployments add even more great functionality that makes it my go-to language.
Pulumi isn't just another tool—it's a paradigm shift in how we perceive and manage cloud infrastructure or really anything with an API! It combines the best in software development with the intricacies of cloud management, resulting in a robust platform that caters to modern development needs with finesse, efficiency, and speed. Whether you're a seasoned systems engineer or a newcomer to the cloud, Pulumi promises—and delivers—a refined, forward-thinking experience that will enhance your velocity and will make your cloud journey even more fun! I highly recommend it!
Pulumi ESC sounds like a significant step forward in managing secrets and configurations across cloud infrastructure and application environments. As cloud infrastructure and application projects grow, handling secrets and configurations becomes increasingly complex, and a dedicated solution for this purpose is essential. I'm sure many organizations will find Pulumi ESC valuable for maintaining security and operational efficiency in their projects. It's great to see innovations like this that simplify cloud management. Best of luck with the launch! 👏🚀
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 when I can compared to yaml or something else. The reason I prefer it is because it does give me more trust, if you are using 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 having to run that code outside of the actual provisioning. This is great for the rare occasions when there might be a missing option in the SDK, which have happened one time over three years with the Azure AD provider. I would argue that most companies do 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 also another feature that 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 also share outputs between different deployments in Pulumi is a killer feature that have simplified a lot of work for us. I often use Pulumi just to deal with configuration for smaller things where I'm testing things out since it is much more secure than copying a file around. Storing secrets in the Pulumi configuration also makes it very easy to get 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 infra structure as code tool I would recommend it is Pulumi!