View possible configuration settings for your package

To view possible configuration settings for a package, run:

tanzu package available get tap.tanzu.vmware.com/$TAP_VERSION --values-schema --namespace tap-install

Note

The tap.tanzu.vmware.com package does not show all configuration settings for packages it plans to install. The package only shows top-level keys. You can view individual package configuration settings with the same tanzu package available get command. For example, to find the keys for Cloud Native Runtimes, you must first identify the version of the package with tanzu package installed list -n tap-install, which lists all the installed packages versions. Then run the command tanzu package available get -n tap-install cnrs.tanzu.vmware.com/CNRS-VERSION --values-schema by using the package version listed for Cloud Native Runtimes.

profile: full

# ...

# For example, CNRs specific values go under its name
cnrs:
  provider: local

# For example, App Accelerator specific values go under its name
accelerator:
  server:
    service_type: "ClusterIP"

The following table summarizes the top-level keys used for package-specific configuration within your tap-values.yaml.

Package	Top-level Key
see table below	shared
API Auto Registration	api_auto_registration
API portal	api_portal
Application Accelerator	accelerator
Application Live View	appliveview
Application Live View connector	appliveview_connector
Application Live View conventions	appliveview-conventions
Cartographer	cartographer
Cloud Native Runtimes	cnrs
Convention controller	convention_controller
Source Controller	source_controller
Supply Chain	supply_chain
Supply Chain Basic	ootb_supply_chain_basic
Supply Chain Testing	ootb_supply_chain_testing
Supply Chain Testing Scanning	ootb_supply_chain_testing_scanning
Supply Chain Security Tools - Scan	scanning
Supply Chain Security Tools - Scan (Grype Scanner)	grype
Supply Chain Security Tools - Store	metadata_store
Build Service	buildservice
Tanzu Application Platform GUI	tap_gui
Learning Center	learningcenter

Shared Keys define values that configure multiple packages. These keys are defined under the shared Top-level Key, as summarized in the following table:

Shared Key	Used By	Description
ca_cert_data	convention_controller, scanning, source_controller	Optional: PEM-encoded certificate data to trust TLS connections with a private CA

For information about package-specific configuration, see Install individual packages.