1. Docs
  2. Pulumi CLI
  3. Commands
  4. pulumi stack graph

pulumi stack graph

Export a stack’s dependency graph to a file


Export a stack’s dependency graph to a file.

This command can be used to view the dependency graph that a Pulumi program emitted when it was run. This graph is output in the DOT format. This command operates on your stack’s most recent deployment.

pulumi stack graph [filename] [flags]


      --dependency-edge-color string   Sets the color of dependency edges in the graph (default "#246C60")
  -h, --help                           help for graph
      --ignore-dependency-edges        Ignores edges introduced by dependency resource relationships
      --ignore-parent-edges            Ignores edges introduced by parent/child resource relationships
      --parent-edge-color string       Sets the color of parent edges in the graph (default "#AA6639")
      --short-node-name                Sets the resource name as the node label for each node of the graph
  -s, --stack string                   The name of the stack to operate on. Defaults to the current stack

Options inherited from parent commands

      --color string                 Colorize output. Choices are: always, never, raw, auto (default "auto")
  -C, --cwd string                   Run pulumi as if it had been started in another directory
      --disable-integrity-checking   Disable integrity checking of checkpoint files
  -e, --emoji                        Enable emojis in the output
      --logflow                      Flow log settings to child processes (like plugins)
      --logtostderr                  Log to stderr instead of to files
      --non-interactive              Disable interactive mode for all commands
      --profiling string             Emit CPU and memory profiles and an execution trace to '[filename].[pid].{cpu,mem,trace}', respectively
      --tracing file:                Emit tracing to the specified endpoint. Use the file: scheme to write tracing data to a local file
  -v, --verbose int                  Enable verbose logging (e.g., v=3); anything >3 is very verbose


Auto generated by spf13/cobra on 19-May-2023