pulumi org member list | CLI commands
Generated for Pulumi CLI v3.245.0.
[EXPERIMENTAL] List members of an organization
Synopsis
[EXPERIMENTAL] List members of an organization.
Returns the members of the organization, showing each member’s user name, role, and join date. Default output is a human-readable table; pass –output=json for the full response as a JSON envelope.
Wraps the ListOrganizationMembers Pulumi Cloud REST endpoint.
pulumi org member list [flags]
Examples
# List members of the default organization.
pulumi org member list
# List members of a specific organization.
pulumi org member list --org acme
# List up to 100 members (auto-paginating as needed).
pulumi org member list --count 100
# Fetch every member, paging through all results.
pulumi org member list --all
# Emit JSON for scripting.
pulumi org member list --output json
Options
--all Fetch every page until the server reports no more results. Mutually exclusive with --count
--count int The number of members to return; if larger than the server page size, additional pages are fetched automatically. Defaults to the size of the first page
-h, --help help for list
--org string The organization to list members for. Defaults to the user's 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
- pulumi org member - [EXPERIMENTAL] Manage organization members
Thank you for your feedback!
If you have a question about how to use Pulumi, reach out in Community Slack.
Open an issue on GitHub to report a problem or suggest an improvement.