porter bundles inspect
porter bundles inspect
Inspect a bundle
Synopsis
Inspect a bundle by printing the invocation 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 [flags]
Examples
porter bundle inspect
porter bundle inspect --reference getporter/porter-hello:v0.1.0
porter bundle inspect --reference localhost:5000/getporter/porter-hello:v0.1.0 --insecure-registry --force
porter bundle inspect --file another/porter.yaml
porter bundle inspect --cnab-file some/bundle.json
Options
--cnab-file string Path to the CNAB bundle.json file.
-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
-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.
Options inherited from parent commands
--debug Enable debug logging
--debug-plugins Enable plugin debug logging
--experimental strings Comma separated list of experimental features to enable. See https://porter.sh/configuration/#experimental-feature-flags for available feature flags.
SEE ALSO
- porter bundles - Bundle commands