Skip to main content
Pulumi logo Pulumi logo
  1. Docs
  2. pulumi policy issue list | CLI commands

pulumi policy issue list | CLI commands

Generated for Pulumi CLI v3.274.1.

    [EXPERIMENTAL] List policy issues for an organization

    Synopsis

    [EXPERIMENTAL] List policy issues for an organization.

    Lists the active policy issues for the organization, or the closed issues when –closed is passed. Each issue represents a violation detected by a Policy Pack during a stack update or a continuous-compliance scan, and includes the violating resource, policy details, status, and enforcement level.

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

    pulumi policy issue list [flags]
    

    Examples

      # List active policy issues
      pulumi policy issue ls
    
      # List all closed policy issues as JSON
      pulumi policy issue ls --closed --all --output json
    
      # List open high and critical severity issues
      pulumi policy issue ls --severity high --severity critical --status open
    
      # List issues for a stack, newest first, as JSON
      pulumi policy issue ls --stack web/prod --sort observedAt:desc --output json
    

    Options

          --account stringArray         Filter by Insights account, as [<project>/]<account> (repeatable)
          --all                         Return all matching issues; mutually exclusive with --count
          --assigned-to stringArray     Filter by assignee login (repeatable)
          --closed                      List closed issues instead of active ones
          --count int                   Maximum number of issues to return (default 100)
          --group stringArray           Filter by policy group (repeatable)
      -h, --help                        help for list
          --org string                  The organization to list policy issues for
          --output string               Output format. Supported values are: default and json (default "default")
          --pack stringArray            Filter by policy pack (repeatable)
          --policy stringArray          Filter by policy name (repeatable)
          --priority stringArray        Filter by priority (repeatable). One of: p0, p1, p2, p3, p4
          --resource-type stringArray   Filter by resource type (repeatable)
          --severity stringArray        Filter by severity (repeatable). One of: low, medium, high, critical
          --sort stringArray            Sort by <field>[:asc|desc], default asc (repeatable). Fields: severity, priority, status, observedAt, lastModified, policyPack, policyName, policyGroupName, resourceType
          --stack stringArray           Filter by stack, as <project>/<stack> (repeatable)
          --status stringArray          Filter by status (repeatable). One of: open, in_progress, by_design, fixed, ignored
          --urn stringArray             Filter by resource URN (repeatable)
    

    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:// or https:// 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

      The infrastructure as code platform for any cloud.