pulumi org role remove | CLI commands

[EXPERIMENTAL] Delete a custom role from an organization

Synopsis

[EXPERIMENTAL] Delete a custom role from an organization.

Removing a role revokes any permissions it had granted to members and teams. If the role is currently assigned, the service rejects the delete unless –force is passed.

By default the command asks for confirmation; pass –yes to skip the prompt. Both –output default and –output json report the deletion outcome, with the JSON form including the organization and role id for scripting.

pulumi org role remove <role-id> [flags]

Examples

  # Delete a role interactively
  pulumi org role remove role-123

  # Delete a role non-interactively, even if it is assigned
  pulumi org role remove role-123 --force --yes

Options

      --force           Force deletion even if the role is currently assigned to members or teams
  -h, --help            help for remove
      --org string      The organization that owns the role. Defaults to the current default organization
      --output string   Output format. Supported values are: default and json (default "default")
  -y, --yes             Skip the confirmation prompt and proceed with deletion

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 org role - [EXPERIMENTAL] Manage organization custom roles