pulumi policy issue edit | CLI commands

[EXPERIMENTAL] Edit the status, priority or assignee of a policy issue

Synopsis

[EXPERIMENTAL] Edit the status, priority or assignee of a policy issue.

At least one of –status, –priority, –assignee or –unassign is required. Invalid flag values or a missing change exit with code 2.

Allowed values: –status open, in_progress, ignored –priority p0, p1, p2, p3, p4 –assignee the Pulumi login of an organization member

Prints the updated issue in the same format as pulumi policy issue get.

pulumi policy issue edit <issue-id> [flags]

Examples

  # Mark a policy issue as in progress
  pulumi policy issue edit <issue-id> --status in_progress

  # Set the priority and assign the issue
  pulumi policy issue edit <issue-id> --priority p1 --assignee <login>

  # Clear the assignee of a policy issue
  pulumi policy issue edit <issue-id> --unassign

Options

      --assignee string   Assign to the Pulumi login of an organization member
  -h, --help              help for edit
      --org string        The organization that owns the issue
      --output string     Output format. Supported values are: default and json (default "default")
      --priority string   Set the priority (p0, p1, p2, p3, p4)
      --status string     Set the status (open, in_progress, ignored)
      --unassign          Clear the assignee

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

• pulumi policy issue - [EXPERIMENTAL] Manage policy issues