Skip to main content
  1. Docs
  2. pulumi org role assign | CLI commands

pulumi org role assign | CLI commands

Generated for Pulumi CLI v3.245.0.

    [EXPERIMENTAL] Assign a role to a team

    Synopsis

    [EXPERIMENTAL] Assign a custom role to a team.

    Each team can hold a single custom role at a time, so running this command replaces the team’s previously assigned role.

    Both –output default and –output json report the assignment, with JSON shaped as an envelope (organization, action, team, roleId) for scripting.

    pulumi org role assign <role-id> <team> [flags]
    

    Examples

      pulumi org role assign role-123 platform
    

    Options

      -h, --help            help for assign
          --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")
    

    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