Finding product dependencies information using the pivnet cli

Products

• VMware Tanzu Application Service
• VMware Tanzu Application Service for VMs

Issue/Introduction

This knowledge base article goes over the process of retrieving product dependencies information for Tanzu products using the pivnet cli.

Resolution

Prerequisites:

Download and install the pivnet cli. It can be downloaded from the following repository: https://github.com/pivotal-cf/pivnet-cli

Browse to https://support.broadcom.com/group/ecx/tanzu-token to get an API_TOKEN value. Specifically, you will need the Legacy API Token as seen in the screenshot below: 

Steps:

Login to the pivnet cli using the token obtained on the previous step.

pivnet login --api-token='my-api-token'

 

You will need a product slug to check the dependencies. To obtain the slug use command:

pivnet products

The output should be similar to the following:

~> pivnet products            
+----+--------------------+--------------------------------+
| ID     |   SLUG         |              NAME              |
+----+--------------------+--------------------------------+
|  1     | <product_1>    | VMware Tanzu Product 1         |
|  2     | <product_2>    | VMware Tanzu Product 2         |
|  3     | <product_3>    | VMware Tanzu Product 3         |
|  4     | <product_4>    | VMware Tanzu Product 4         |
|  5     | <product_5>    | VMware Tanzu Product 5         |
+----+--------------------+--------------------------------+

Once you have the product slug, you can check the product for releases to find the specific release you are interested in. The following example show 10 releases for a product:

~> pivnet releases -p <product_slug> -l 10
+--------+---------+-------------+--------------------------+
|   ID   | VERSION | DESCRIPTION |        UPDATED AT        |
+--------+---------+-------------+--------------------------+
| xxxxxx | x.x.x   | <prod_desc> | xxxx-xx-xxTxx:xx:xx.000Z |
| xxxxxx | x.x.x   | <prod_desc> | xxxx-xx-xxTxx:xx:xx.000Z |
| xxxxxx | x.x.x   | <prod_desc> | xxxx-xx-xxTxx:xx:xx.000Z |
| xxxxxx | x.x.x   | <prod_desc> | xxxx-xx-xxTxx:xx:xx.000Z |
| xxxxxx | x.x.x   | <prod_desc> | xxxx-xx-xxTxx:xx:xx.000Z |
| xxxxxx | x.x.x   | <prod_desc> | xxxx-xx-xxTxx:xx:xx.000Z |
| xxxxxx | x.x.x   | <prod_desc> | xxxx-xx-xxTxx:xx:xx.000Z |
| xxxxxx | x.x.x   | <prod_desc> | xxxx-xx-xxTxx:xx:xx.000Z |
| xxxxxx | x.x.x   | <prod_desc> | xxxx-xx-xxTxx:xx:xx.000Z |
| xxxxxx | x.x.x   | <prod_desc> | xxxx-xx-xxTxx:xx:xx.000Z |
+--------+---------+-------------+--------------------------+

Using the release selected you can see a list of release dependencies using the following command:

pivnet release-dependencies -p <product_slug> -r <prod_release>

The command will output a full list of the dependencies and its releases.This list will include other tiles and stemcells.