TerraformPilot

Infrastructure as Code

Pulumi v3.277.0: pulumi delivery register, Automation API preview(), and CheckConfig2

Pulumi v3.277.0 adds a preview delivery register CLI command, Automation API preview() in NodeJS/Python/Go, and provider CheckConfig2. Upgrade and verification steps included.

LLuca Berton3 min read

Introduction

#

Pulumi v3.277.0 was released on 2026-11-18, following v3.276.0. This release introduces a preview CLI command for Pulumi Delivery, extends the Automation API with a preview method, adds a new provider protocol method, and includes several fixes and small improvements. This article covers what matters for teams writing and running Pulumi programs day to day.

What Is New

#

pulumi delivery register (preview)

#

A new preview command registers the Pulumi Delivery pipeline that a program declares (#25729):

pulumi delivery register

This is marked as a preview feature, so expect behavior and flags to evolve in future releases. Treat it as experimental in production workflows.

Automation API: preview() for NodeJS, Python, and Go

#

The generated Automation API now exposes a preview method for NodeJS, Python, and Go SDKs (#25054). This lets automation scripts run a dry-run preview without going through the CLI directly.

NodeJS example:

const stack = await LocalWorkspace.createOrSelectStack({ stackName, projectName, program });
const previewResult = await stack.preview();
console.log(previewResult.stdout);

Python example:

stack = auto.create_or_select_stack(stack_name=stack_name, project_name=project_name, program=pulumi_program)
preview_result = stack.preview()
print(preview_result.stdout)

Go example:

previewResult, err := stack.Preview(ctx)
if err != nil {
    return err
}
fmt.Println(previewResult.StdOut)

Provider protocol: CheckConfig2

#

The engine adds a CheckConfig2 method to the provider protocol, with its own request and response types (#25670). This is primarily relevant to provider authors implementing the resource provider gRPC interface; it does not change HCL/program-level syntax but is worth tracking if you maintain a custom provider.

pulumi state move --parent

#

The pulumi state move command gains a --parent flag to parent moved resources under a resource in the destination stack (#25697):

pulumi state move \
  --source-stack my-org/my-project/dev \
  --parent urn:pulumi:dev::my-project::aws:s3/bucket:Bucket::target-parent \
  urn:pulumi:dev::old-project::aws:s3/bucket:Bucket::my-bucket

This is useful when consolidating stacks and you need the moved resource to sit under an existing parent resource rather than at the top level.

Go SDK: property.Map.Keys()

#

The Go SDK adds a Keys() method to property.Map, giving plugin and provider authors a direct way to enumerate map keys (#25712).

Bug Fixes Worth Knowing

#
  • pulumi convert --help now has the correct blank line between the target languages list and example usage (#22559).
  • Plan violations found while finalizing stack outputs are now reported instead of silently failing the update (#25629). If you rely on up --plan, this surfaces errors that were previously swallowed.
  • up --plan no longer fails in the NodeJS SDK when a stack output is a whole resource (#25629).
  • The tree renderer display is fixed while installing plugins (#25655).
  • pulumi package publish reference docs formatting is fixed (#25695).
  • Python SDK generation now emits the license as an SPDX string in generated pyproject.toml files (#25735).

Other Improvements

#
  • The project confirmation step in the guided pulumi new flow is easier to read (#25663).

Dependency Bumps

#

As part of #25751, several language/runtime components were upgraded:

  • .NET SDK to v3.120.0
  • YAML support to v1.39.2
  • HCL support to v0.20.1
  • Java SDK to v1.40.2

No breaking changes or deprecations are called out in these release notes.

Upgrade Steps

#

Update the Pulumi CLI directly:

curl -fsSL https://get.pulumi.com | sh -s -- --version 3.277.0

Or via a package manager, for example Homebrew:

brew upgrade pulumi

If pinning the CLI or SDK version in CI, update the constraint accordingly, for example in a NodeJS package.json:

{
  "dependencies": {
    "@pulumi/pulumi": "^3.277.0"
  }
}

For projects using a provider plugin version lock, refresh plugins after upgrading the CLI:

pulumi plugin install

Verify

#

Confirm the CLI is on the new version:

pulumi version

Expected output: v3.277.0

Run a preview against an existing stack to confirm the engine and provider changes behave as expected:

pulumi preview

If using the Automation API's new preview() method, run the automation script and confirm it returns a preview result without invoking the CLI manually.

Conclusion

#

v3.277.0 is a moderate release: the headline items are the preview pulumi delivery register command, Automation API preview() support for NodeJS, Python, and Go, and the --parent flag for pulumi state move. None of the changes require HCL rewrites, but teams using up --plan should note that previously silent plan violations are now reported. Upgrade via the standard CLI install path and re-run pulumi plugin install to pick up any provider refresh. Full details are on the release page.

#Pulumi#Automation API#CLI#Provider Protocol#State Management

Share this article