pulumi org audit-log list | CLI commands

[EXPERIMENTAL] List audit log events for an organization

Synopsis

[EXPERIMENTAL] List audit log events for an organization.

Returns audit log events for the organization. Results may be filtered by event type and by the user that triggered the event. Use –start-time to bound the upper end of the time range.

Default output is a human-readable table; pass –output=json for the full response as a JSON envelope.

pulumi org audit-log list [flags]

Options

      --all                 Return all matching events; mutually exclusive with --count
      --count int           Maximum number of events to return. Defaults to the size of the first page; larger values auto-paginate
      --event-type string   Filter by event type
  -h, --help                help for list
      --org string          The organization to list audit logs for
      --output string       Output format. Supported values are: default and json (default "default")
      --start-time string   The upper bound of the time range (V1 semantics)
      --user string         Filter by user login

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 audit-log - [EXPERIMENTAL] Inspect organization audit logs