Posts Tagged features

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.

Read more →

Pulumi’s previews are an important part of any workflow where you want to see the changes that will be made to your infrastructure before actually making the changes (with pulumi up). However, today there is no guarantee that the pulumi up operation will do only what was previewed; if the program, or your infrastructure, changes between the preview and the update, the update might make additional changes to bring your infrastructure back in line with what’s defined in your program. We’ve heard from many of you that you need a strong guarantee about exactly which changes an update will make to your infrastructure, especially in critical and production environments.

Read more →

Over the holidays we have been releasing new features and improvements. Read on to learn about what’s new in this release!

• Cloud Providers and Packages
  • New Command package
  • Support pulumi import for Kubernetes CRDs
  • Various improvements to Helm Release
• Pulumi CLI and core technologies
  • Support using native ES modules as Pulumi scripts
  • Support packages with plugins hosted in any third-party location
  • State locking default enabled
• Pulumi Service
  • Audit logging for third-party secrets managers

Read more →

As a reader of this blog, you’ve probably heard of the Pulumi Service, the default state-management backend of the Pulumi CLI, and if that’s the case, there’s a good chance you’ve also heard of many of its key features. But did you know we’re adding new features to the Service all the time—some of which are incredibly easy to miss? In this post, we’ll highlight a few of those lesser-known features that we think make it even easier to manage your infrastructure with Pulumi.

Read more →

As part of our hackathon near the end of last year, we decided to explore solutions to a common problem when people are using Pulumi for their systems. A question that’s been asked in a few different forms is how to resolve circular dependencies between resources in a Pulumi program.

Read more →

With the holiday season approaching, we’ve been focused on tidying up our products, delivering asks we’ve heard from you in GitHub and at conferences, and looking ahead to 2022! Read on to learn about what’s new this release:

• Pulumi Registry, Pulumi Packages, & integrations
  • Helm Release resource supports local charts
  • New examples for the Kubernetes native provider
  • New resources in the AWS Native provider
  • New resources in the Azure Native provider
  • Support for Kubernetes 1.23
• Pulumi CLI and core technologies
  • Exclude protected resources from pulumi destroy
  • Pulumi Package plugins can now be hosted on GitHub Releases
• Pulumi Service & Pulumi.com
  • More ways to share invites to your organization
  • Self-Hosted Pulumi Service can disable email sign-up and login

Read more →

It’s been another exciting few weeks here at Pulumi! We’ve caught our breath from Cloud Engineering Summit (don’t forget to check out the talks if you haven’t yet!) and we’re back to adding new value and highly-requested fixes across the Pulumi Cloud Engineering Platform. Read on to learn about new providers, new enhancements to the core Pulumi experience, and more!

• Pulumi Registry, Pulumi Packages, & integrations
  • dependsOn can now await a fully-deployed Helm Chart resource
  • New provider: Elastic Cloud
  • AWS Native provider supports auto-naming
  • New resources in the AWS Native provider
  • New resources in the Azure Native provider
• Pulumi CLI and core technologies
  • Functions now support outputs
  • --json flag for pulumi {update|destroy|preview|refresh}
  • Python 3.6 support will be deprecated soon
• Pulumi Service & Pulumi.com
  • Set the default organization for newly-created stacks

Read more →

Pulumi 3.17.1 makes it easier to compose function calls and resources. In practice you often need to call a function with a resource output. Previous versions of Pulumi required an apply to do this, which was unfortunate:

• new Pulumi users would get stuck and ask for help as the solution was not obvious

• experienced users found the code unpleasant, upvoting the relevant GitHub Issue

With Pulumi 3.17.1 you can now call functions directly with resource outputs without an extra apply. Every function now has an additional Output form that accepts Input-typed arguments and returns an Output-wrapped result.

For a quick example, here is how you can call aws.ecr.getCredentials with a registryId of type Output<string>:

const registryId: Output<string> = ...
getCredentialsOutput({registryId: registryId}): Output<GetCredentialsResult>

registry_id: Output[str] = ...
get_credentials_output(registry_id=registryId): Output[GetCredentialsResult]

var registryId StringOutput
var result GetCredentialsResultOutput
result = GetCredentialsOutput(ctx, GetCredentialsOutputArgs{
    RegistryId: result
})

Output<string> registryId;
GetCredentials.Invoke(new GetCredentialsInvokeArgs
{
   RegistryId = registryId
});

Read more →

It’s been an incredibly busy few weeks at Pulumi. We’ve met thousands of you at our second annual Cloud Engineering Summit, shipped major new releases like Pulumi Registry and Pulumi Kubernetes Operator 1.0 and continued to innovate on and improve the entire Pulumi Cloud Engineering Platform. Get caught up on Cloud Engineering Summit to learn what’s coming in cloud engineering, or read on for this month’s news.

• Cloud Engineering Summit
• Pulumi Registry, Pulumi Packages, & integrations
  • Pulumi Registry: your window to the cloud
  • Pulumi Kubernetes Operator 1.0
  • New resources in the Azure Native provider
• Pulumi CLI and core technologies
  • Resource methods for Pulumi Packages
  • Automation API: delete, unprotect state in .NET
• Pulumi Service & Pulumi.com
  • Automated audit log export

Read more →

Pulumi offers the most complete infrastructure as code platform for building, deploying, and managing modern cloud infrastructure and applications. When you use Pulumi, a vast library of cloud resources—from compute, storage, and other cloud infrastructure to databases to identity providers to monitoring systems—is at your fingertips. As the Pulumi community has grown, we’ve heard from many of you that we needed a central hub where you could find all of those resources. We’ve also heard from Pulumi partners that they wanted a great place to showcase their integrations with Pulumi so that their customers can more easily learn how to use Pulumi to deploy and manage their products.

Today, we’re excited to launch Pulumi Registry, the one place to discover and share everything you can achieve using Pulumi. Pulumi Registry is a searchable collection of Pulumi Packages published by Pulumi and our partners. With Pulumi Registry, you can easily find the package with the resources you need, install that package directly into your project, and start building. You can choose from Providers that give you full access to everything a cloud provider has to offer, or choose a Component that gets you started quickly with best practices and sensible defaults baked in. All Pulumi Packages are available in all Pulumi languages, so you can build your infrastructure using C#, Go, Python, and TypeScript/JavaScript. You’ll also find all of the documentation you need to succeed: from detailed API reference to how-to guides with source code for specific use cases.

Read more →