pulumi insights account scan get | CLI commands

[EXPERIMENTAL] Get details for a specific Insights scan

Synopsis

[EXPERIMENTAL] Get details for a specific Pulumi Insights scan.

Returns the workflow run for a single scan: status, timing, and the list of jobs (with their step-level status). Use account scan list to discover recent scan IDs, and account scan log to fetch the raw log output for a step.

Default output is a human-readable summary; pass –output=json for the full response as JSON.

pulumi insights account scan get <account> <scan-id> [flags]

Examples

  # Get the details of a specific scan.
  pulumi insights account scan get prod-aws/us-east-1 7bb80f16-…

  # Pipe a recent scan ID into `get` for the full workflow run.
  pulumi insights account scan list prod-aws --output json |
    jq -r '.scans[0].id' | xargs pulumi insights account scan get prod-aws/us-east-1

  # Emit JSON for scripting (includes the per-step status).
  pulumi insights account scan get prod-aws/us-east-1 7bb80f16-… --output json

Options

  -h, --help            help for get
      --org string      Organization that owns the Insights account (defaults to the current default org)
      --output string   Output format. Supported values are: default and json (default "default")

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
  -Q, --fully-qualify-stack-names    Show fully-qualified stack names
      --logflow                      Flow log settings to child processes (like plugins)
      --logtostderr                  Log to stderr instead of to files
      --memprofilerate int           Enable more precise (and expensive) memory allocation profiles by setting runtime.MemProfileRate
      --non-interactive              Disable interactive mode for all commands
      --otel-traces string           Export OpenTelemetry traces to the specified endpoint. Use file:// for local JSON files, grpc:// for remote collectors
      --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

SEE ALSO

• pulumi insights account scan - [EXPERIMENTAL] Trigger a resource discovery scan for an Insights account