Pulumi Secrets Management
Pulumi community member Sanjay Bhagia explores using Pulumi to manage secrets.
This blog post discusses hierarchical config before Pulumi ESC was released. ESC makes hierarchical config easy.
Pulumi Release Notes: Pulumi Import Improvements, RetainOnDelete as a resource option, and more!
The team has been busy releasing new features and improvements in the last 3 weeks. Read on to learn about what’s new in this release!
- Pulumi CLI and core technologies
Hierarchical Config: The Interim Solution
A really common question that we receive on the Pulumi team is, “How can we set config at a project level, that can be used across all stacks?”.
When I say “really common” … I mean really, really common.
This issue was first open in 2018 and has received 52 votes from the community. Not only that, we’ve had plenty of similar issues created over the years too.
Easier IaC adoption with improved `pulumi import` experience
Last year, we introduced a new Pulumi feature that allows you to import existing infrastructure into your Pulumi program. Not only did it bring the resource into the Pulumi state file, but it could generate the source code for your Pulumi program too. Today, we’re excited to announce that we’ve listened to feedback and delivered a plethora of updates and fixes to streamline the import experience; to make it more useful, more convenient, and more powerful.
Deploy MERN Stack on DigitalOcean with Pulumi [Guide]
![Deploy MERN Stack on DigitalOcean with Pulumi [Guide]](/blog/fullstack-pulumi-mern-stack-digitalocean/meta.png)
As a developer, I get lots of ideas for web apps—little things, mostly: nifty ways to keep track of my kids’ allowances, habit trackers, shopping lists. Most of them, however, never see the light of day, and not just because I’m lazy; I also tend to get hung up trying to decide what to use for the technology stack.
Upgrade Strategies: An Introduction for IaC
When you’re working with infrastructure, you’re inevitably going to need to upgrade or update that infrastructure. Whether it’s an operating system update or a desire to get CPU or memory upgrades, you will need the ability to pick resources and change them as necessary. In the past, this kind of upgrade would be done on the basis of individual resources, with each one being updated and checked either by hand or programmatically before moving onto the next resource. If you’ve ever done a database migration or if you ever did the recommended way of upgrading your computer’s operating system including all of the backup steps, you’re familiar with this process. Stand up the new resource. Check everything works. Move over the data. Check again. Tear down the old infrastructure. In a cloud computing environment, though, you’re often dealing with hundreds or thousands of resources, and doing one-by-one replacement is a nightmare that takes ages. However, there are other options, many borrowed from the application deployment world, that we have available to us because we write infrastructure as code.
Introducing Pulumi Business Critical Edition for Enterprise Modernization
In the last 12 months, we have experienced 350% year-over-year growth of our enterprise customers, including Mercedes-Benz, Snowflake, Atlassian and SANS Institute. Given the growth in our enterprise customer base, we are excited to launch today a new Business Critical Edition for the Pulumi Service, a 30 day Self-Hosted Pulumi Service trial, and the option to purchase Pulumi Enterprise and Business Critical through the AWS Marketplace!
February Releases: Update Plans public preview, Helm Release for Kubernetes GA and new Pulumi Service sign-in experience
The team has been busy releasing new features and improvements in the last 3 weeks. Read on to learn about what’s new in this release!
- Cloud Providers and Packages
- Pulumi CLI and core technologies
- Pulumi Service
Retain on Delete
Pulumi is frequently used to manage the entire lifecycle of a resource, from creation, to updates, to replacement, to deletion. However, there are some cases where it is important to ensure that a resource’s life can extend beyond the lifetime of the Pulumi program that created it. To support these use cases, Pulumi now supports a new resource option RetainOnDelete which allows a resource to be retained in a cloud provider even after it is deleted from the Pulumi stack it is part of.
Migrating My Infrastructure From Terraform to Pulumi
Pulumi community member Erik Näslund shares his thoughts on how to migrate from Terraform to Pulumi. Read on to learn all the details of his experience!