Porter Documentation
References
porter bundles inspect

porter bundles inspect

porter bundles inspect

Inspect a bundle

Synopsis

Inspect a bundle by printing the bundle images and any related images images.

If you would like more information about the bundle, the porter explain command will provide additional information, like parameters, credentials, outputs and custom actions available.

porter bundles inspect REFERENCE [flags]

Examples 

  porter bundle inspect
  porter bundle inspect ghcr.io/getporter/examples/porter-hello:v0.2.0
  porter bundle inspect localhost:5000/ghcr.io/getporter/examples/porter-hello:v0.2.0 --insecure-registry --force
  porter bundle inspect --file another/porter.yaml
  porter bundle inspect --cnab-file some/bundle.json

Options 

      --autobuild-disabled                     Do not automatically build the bundle from source when the last build is out-of-date.
      --cnab-file string                       Path to the CNAB bundle.json file.
      --dependencies-version-strategy string   Strategy for resolving dependency version ranges. Allowed values: exact, max-patch, max-minor, min.
  -f, --file porter.yaml                       Path to the Porter manifest. Defaults to porter.yaml in the current directory.
      --force                                  Force a fresh pull of the bundle
  -h, --help                                   help for inspect
      --insecure-registry                      Don't require TLS for the registry
      --max-dependency-depth int               Maximum depth to traverse when showing dependencies (default 10)
  -o, --output string                          Specify an output format.  Allowed values: plaintext, json, yaml (default "plaintext")
  -r, --reference string                       Use a bundle in an OCI registry specified by the given reference.
      --show-dependencies                      Show the full dependency tree of the bundle

Options inherited from parent commands 

      --context string         Name of the configuration context to use. When unset, Porter uses the current-context from the config file, falling back to the context named "default".
      --experimental strings   Comma separated list of experimental features to enable. See https://porter.sh/configuration/#experimental-feature-flags for available feature flags.
      --verbosity string       Threshold for printing messages to the console. Available values are: debug, info, warning, error. (default "info")

SEE ALSO

porter bundles explainporter bundles lint