Skip to main content
Sign in Dashboard Get started
  1. Docs
  2. pulumi insights resource get | CLI commands

pulumi insights resource get | CLI commands

Generated for Pulumi CLI v3.242.0.

    [EXPERIMENTAL] Get a single resource discovered by Pulumi Insights

    Synopsis

    [EXPERIMENTAL] Look up a single resource discovered by Pulumi Insights.

    The positional argument identifies the resource within an Insights account, in the <type>::<id> form described by the Pulumi Cloud REST API (e.g. aws:s3/bucket:Bucket::my-bucket). The account is selected with –account; the organization defaults to the current default org and can be overridden with –org.

    Wraps the ReadResource Pulumi Cloud REST endpoint.

    pulumi insights resource get <resource-type-and-id> [flags]

    Examples

      # Look up a resource in a specific Insights account.
  pulumi insights resource get --account prod-aws 'aws:s3/bucket:Bucket::my-bucket'

  # Override the organization.
  pulumi insights resource get --org acme --account prod-aws \
      'aws:s3/bucket:Bucket::my-bucket'

  # Emit JSON for scripting.
  pulumi insights resource get --account prod-aws \
      'aws:s3/bucket:Bucket::my-bucket' --output json

    Options

          --account string   Insights account containing the resource
  -h, --help             help for get
      --org string       Organization that owns the Insights account (defaults to the current default org)
      --output string    Output format. One of: default, 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