Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update index.md #14276

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 6 additions & 5 deletions content/blog/announcing-public-preview-update-plans/index.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,7 @@
---
title: "Announcing the public preview of Update Plans"
title: "Announcing the Public Preview of Update Plans"
date: 2022-02-09
updated: 2024-03-05
meta_desc: Update Plans enable you to see and confirm the updates that will be made to your infrastructure and then apply those updates at a later time.
meta_image: update_plans_preview.png
authors:
Expand All @@ -13,9 +14,9 @@ Pulumi’s previews are an important part of any workflow where you want to see

<!--more-->

Today, I’m excited to announce the public preview of Update Plans, a new Pulumi feature which guarantees that operations shown in `pulumi preview` will run on `pulumi up`. Update Plans also help catch any unexpected changes that might happen between when you preview a change and when you apply that change. Update Plans work by saving the results of a `pulumi preview` to a _plan file_, which enables you to restrict subsequent `pulumi up` operations to only the actions saved in the plan file. This helps you ensure that what you saw in the `pulumi preview` is what will actually happen when you run `pulumi up`.
Today, I’m excited to announce the public preview of [Update Plans](/docs/iac/concepts/update-plans/), a new Pulumi feature which guarantees that operations shown in `pulumi preview` will run on `pulumi up`. Update Plans also help catch any unexpected changes that might happen between when you preview a change and when you apply that change. Update Plans work by saving the results of a `pulumi preview` to a _plan file_, which enables you to restrict subsequent `pulumi up` operations to only the actions saved in the plan file. This helps you ensure that what you saw in the `pulumi preview` is what will actually happen when you run `pulumi up`.

Here’s an example of Update Plans in action. In this example we're creating a new AWS EC2 instance and associated security group. First, we plan the change with `pulumi preview --save-plan plan.json`, and then we examine the plan file to see which resources the plan expects to change. Finally, we run an update that's constrained to the plan with `pulumi up --plan plan.json`.
Here’s an example of Update Plans in action. In this example we're creating a new [AWS EC2](https://aws.amazon.com/ec2/) instance and associated security group. First, we plan the change with `pulumi preview --save-plan plan.json`, and then we examine the plan file to see which resources the plan expects to change. Finally, we run an update that's constrained to the plan with `pulumi up --plan plan.json`.

{{< asciicast id="466347" >}}

Expand All @@ -25,7 +26,7 @@ To get started, you only need to add `--save-plan <file>` to the preview command

When updates fail to validate against the plan, Pulumi will print what constraint failed. In the example above, the resource `urn:pulumi:dev::aws-ts-webserver::aws:ec2/instance:Instance::web-server-www` changed the value of the property `userData`.

## New scenario enabled by Update Plans: pull request validation workflows
## New Scenario: Pull Request Validation Workflows

Software development teams commonly use version control-based workflows to review and monitor the code that is added to a codebase. For example, many teams protect their primary branch (e.g. `main`, `master`, `trunk`) from direct code pushes and instead require a pull or merge request where the changes can be reviewed and continuous integration (CI) and tests can be run.

Expand All @@ -39,7 +40,7 @@ Update Plans are in public preview. We recommend using it only in non-critical,

{{% /notes %}}

We’re eager for you to try the public preview of Update Plans and let us know what you think. To try it out, make sure you’ve updated to Pulumi [3.24.1](https://github.com/pulumi/pulumi/releases/tag/v3.24.1) then set the following environment variable in your shell:
We’re eager for you to try the public preview of Update Plans and let us know what you think. To try it out, make sure you’ve updated to [Pulumi 3.24.1](https://github.com/pulumi/pulumi/releases/tag/v3.24.1) then set the following environment variable in your shell:

```sh

Expand Down
Loading