pulumi-stack-history

Display history for the current stack

$ pulumi stack [[hist|history]]

$ pulumi stack [[hist|history]] --full-dates

$ pulumi stack [[hist|history]] [[-j|--json]]

$ pulumi stack [[hist|history]] [[-s|--stack]] [stack_name]

$ pulumi stack [[hist|history]] [[-h|--help]]

pulumi stack history [stack_name] [options]

-s, --stack string
    The name of the stack to operate on. If omitted, the currently selected stack's history is shown.

--json
    Emit output as JSON, which is useful for programmatic consumption and integration with other tools.

--show-secrets
    Display secret values in the history output. Use with extreme caution due to security implications.

--show-url
    Display the URL to the update in the Pulumi Cloud console (if using the Pulumi Cloud backend).

The pulumi stack history command provides a chronological record of all updates performed on a specific Pulumi stack.

It is an essential tool for understanding the evolution of your infrastructure, debugging issues, and auditing deployments. Each history entry typically includes the unique update ID, the timestamp when the update began, the duration of the update, the identity of the user who initiated the update, and its final status (e.g., succeeded, failed, canceled).

This command helps track changes, identify who made them, and when, offering valuable insights into the lifecycle of your cloud resources managed by Pulumi. It can be particularly useful for reviewing deployment timelines, analyzing performance of updates, and quickly pinpointing the state of a stack at any given point in its history.

The command requires a Pulumi project and a selected stack, or a stack name provided as an argument.
The history is stored in the Pulumi backend (local, cloud, S3, etc.) and its availability depends on the backend's configuration.
Using --show-secrets should be done with extreme caution due to the sensitive nature of secret values, as it can expose credentials or other confidential information.

The command typically displays columns such as ID, UPDATE TIME, DURATION, USER, and STATUS. The ID is a unique identifier for each update, which is useful for referencing specific deployments (e.g., for `pulumi stack restore --update `).

Pulumi was founded in 2017 to enable infrastructure as code using general-purpose programming languages. The stack history command is a fundamental component of the Pulumi CLI, present since early versions, as robust deployment tracking is crucial for any Infrastructure as Code (IaC) platform. Its development has consistently focused on clarity of output, operational robustness, and seamless integration with various backend providers.

pulumi stack ls(1), pulumi stack select(1), pulumi up(1), pulumi destroy(1), pulumi stack export(1), pulumi stack restore(1)