pulumi org member remove | CLI commands

[EXPERIMENTAL] Remove a member from an organization

Synopsis

[EXPERIMENTAL] Remove a member from an organization.

Removes a user from an organization. The removed user loses access to all organization resources including stacks, teams, and projects. This cannot be undone. You will be prompted to confirm unless –yes is passed.

pulumi org member remove <user-login> [flags]

Examples

  # Remove a member (will prompt for confirmation)
  pulumi org member remove alice

  # Remove without confirmation
  pulumi org member remove alice --yes

Options

  -h, --help            help for remove
      --org string      The organization that owns the member
      --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 org member - [EXPERIMENTAL] Manage organization members