pulumi policy group remove | CLI commands

[EXPERIMENTAL] Delete a Policy Group

Synopsis

[EXPERIMENTAL] Delete a Policy Group.

Deletes a Policy Group from an organization. This cannot be undone. You will be prompted to confirm unless –yes is passed.

The organization’s default Policy Group cannot be deleted. Deleting a Policy Group removes all policy enforcement associations for the stacks that were assigned to it.

pulumi policy group remove <name> [flags]

Examples

  # Remove a Policy Group (will prompt for confirmation)
  pulumi policy group remove prod-policies

  # Remove without confirmation
  pulumi policy group remove prod-policies --yes

  # Remove from a specific organization
  pulumi policy group remove prod-policies --org acme --yes

Options

  -h, --help            help for remove
      --org string      The organization that owns the Policy Group
      --output string   Output format. Supported values are: default and json (default "default")
  -y, --yes             Skip confirmation prompts

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 policy group - Manage policy groups