pulumi template list | CLI commands

[EXPERIMENTAL] List registry-backed templates

Synopsis

[EXPERIMENTAL] List templates from the Pulumi Cloud registry.

No authentication is required; without a Pulumi Cloud session, only publicly visible templates are returned.

Results are paginated by the server; the command follows continuation tokens internally so all matching templates are streamed in a single invocation.

pulumi template list [flags]

Examples

  # List every visible registry template.
  pulumi template list

  # Filter by template name.
  pulumi template list --name aws-quickstart

  # Filter to templates owned by a specific organization.
  pulumi template list --org myorg

  # Free-text search across name, display name, description, metadata, and runtime.
  pulumi template list --search serverless

  # Emit JSON for scripting.
  pulumi template list --output json

Options

  -h, --help            help for list
      --name string     Filter to templates whose name matches the given value
      --org string      Filter to templates owned by the given organization
      --output string   Output format. One of: default, json (default "default")
      --search string   Free-text search across name, display name, description, metadata values, and runtime

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 template - Work with Pulumi templates