1. Docs
  2. Pulumi CLI
  3. Commands
  4. pulumi org search

pulumi org search

    Search for resources in Pulumi Cloud

    Synopsis

    Search for resources in Pulumi Cloud.

    pulumi org search [flags]
    

    Options

          --delimiter Delimiter   Delimiter to use when rendering CSV output. (default )
      -h, --help                  help for search
          --org string            Name of the organization to search. Defaults to the current user's default organization.
      -o, --output outputFormat   Output format. Supported formats are 'table', 'json', 'csv', and 'yaml'.
      -q, --query stringArray     A Pulumi Query to send to Pulumi Cloud for resource search.May be formatted as a single query, or multiple:
                                  	-q "type:aws:s3/bucket:Bucket modified:>=2023-09-01"
                                  	-q "type:aws:s3/bucket:Bucket" -q "modified:>=2023-09-01"
                                  See https://www.pulumi.com/docs/pulumi-cloud/insights/search/#query-syntax for syntax reference.
          --web                   Open the search results in a web browser.
    

    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
          --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

    Auto generated by spf13/cobra on 5-Jun-2024
      Introducing Pulumi Copilot - Intelligent Cloud Management