pulumi insights account scan list | CLI commands
Generated for Pulumi CLI v3.242.0.
[EXPERIMENTAL] List recent scans for an Insights account
Synopsis
[EXPERIMENTAL] List recent scans for a Pulumi Insights account.
The positional argument is the Insights account. For parent accounts the
endpoint returns scans across every child account, so this is the
recommended way to discover scan IDs to feed into account scan log.
By default the command returns a single page of results. –count N returns at most N results. –all (equivalent to –count 0) returns every matching scan. –count and –all are mutually exclusive.
pulumi insights account scan list <account> [flags]
Examples
# List the most recent scans for an account.
pulumi insights account scan list prod-aws
# For a parent account, the result spans every child account.
pulumi insights account scan list prod-aws
# Narrow to a single child by passing its full account path.
pulumi insights account scan list prod-aws/us-east-1
# Return at most 25 scans.
pulumi insights account scan list prod-aws --count 25
# Return every scan.
pulumi insights account scan list prod-aws --all
# Emit JSON for scripting.
pulumi insights account scan list prod-aws --output json
Options
--all Return every matching scan
--count int Return at most this many scans (--count 0 is equivalent to --all)
-h, --help help for list
--org string Organization that owns the Insights account (defaults to the current default org)
--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 insights account scan - [EXPERIMENTAL] Trigger a resource discovery scan for an Insights account
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.