pulumi-stack-hist

View documentation for the original command

$ tldr pulumi stack history

pulumi-stack-hist [stack-name] [--json] [--show-secrets] [--max-count int]

stack-name
    The name of the Pulumi stack whose history is to be displayed. If omitted, the currently selected stack is used.

--json
    Emits the stack history output in machine-readable JSON format.

--show-secrets
    Displays secret values that are part of the stack's history. Use with extreme caution as this exposes sensitive information.

--max-count int
    Specifies the maximum number of history records to display. The default is typically 100.

The pulumi-stack-hist command provides a detailed chronological record of all updates performed on a specific Pulumi stack. Each entry in the history typically includes information such as the unique update ID, the time the update was initiated, the duration of the update, the user who performed it, and its final status (e.g., succeeded, failed, pending). This command is invaluable for auditing changes, debugging issues by pinpointing when a problem might have been introduced, and understanding the evolution of infrastructure over time. It helps maintain accountability and provides a clear lineage of infrastructure state transformations. Users can inspect past deployments to trace configuration changes, resource modifications, or policy adjustments. The command supports various options to refine the output, such as displaying the history in JSON format for programmatic consumption or adjusting the number of records displayed.

Using the --show-secrets flag can expose sensitive information. Exercise extreme caution and ensure appropriate security measures are in place when using this option, especially in shared or logged environments.
The command displays a high-level overview of updates; for detailed diffs between specific update versions, further Pulumi commands or tooling might be required.

pulumi-stack-hist is primarily used for auditing, debugging, and understanding the lifecycle of infrastructure. It provides crucial context for operational teams and developers to trace back changes that might have led to current infrastructure states or issues.

By default, the output is presented in a human-readable table format. When the --json flag is used, it provides a structured JSON array, making it suitable for scripting and integration with other tools for automated reporting or analysis.

The functionality represented by pulumi-stack-hist is an integral part of the Pulumi CLI, which emerged with the Pulumi platform itself. Pulumi was founded in 2017 and publicly launched in 2018, aiming to enable developers to define, deploy, and manage cloud infrastructure using familiar programming languages. As a core aspect of infrastructure as code (IaC) is audibility and state management, the ability to view a stack's history was a foundational component, allowing users to track the evolution of their infrastructure deployments from day one. Its design reflects the need for clear visibility into who changed what and when, supporting both individual developer workflows and team-based infrastructure management.

pulumi(1), pulumi stack(1), pulumi stack select(1), pulumi stack ls(1), pulumi stack refresh(1)