Tanzu Network to Broadcom’s Customer Support Portal Transition - Automation Impact
Article ID: 370181
Updated On:
Products
Issue/Introduction
Starting on June 24th 2024, all on-premise Tanzu products will be distributed on Broadcom's Customer Support Portal (https://support.broadcom.com). The impact to Tanzu Network automation tools is clarified below.
Environment
Keywords:
- TanzuNet
- Tanzu
- Download
- Pivnet
- Platform
- Automation
Environment:
- TanzuNet
- Tanzu Network
- Customer Connect
- Tanzu
- Download
- Pivnet
- Platform Automation
- Pipeline
Resolution
How can I discover new versions of products? How can I obtain the product slug ID?
The existing Tanzu Network API has been replicated for most use cases, and the product/releases endpoints will continue to function.. Users will be able to get JSON formatted responses with information on products, slugs, and releases, including:
- GET /api/v2/products
- Returns a list of products
- Includes slug information
- GET /api/v2/products/:product_slug/releases
- Returns releases associated with the specified product
The slug ID is not currently user-facing in Support Portal UI directly or via the url like in Tanzu Network today. Instead, the information will be solely discovered via the replicated API.
Existing pivnet CLI commands may continue to function, but since the existing Tanzu Network API is not being fully replicated, some commands, flags, and options may not function fully.
How can I get dependency and upgrade path information?
This information exists but is not currently available via Support Portal UI. Instead, users can continue to get this information via Tanzu Network replicated API. For example:GET /api/v2/products/{product_slug}/releases/{release_id}/dependencies- Returns dependency information for the specific release
How can I get lifecycle information?
Users can access lifecycle information such as General Availability (GA) and End of Support (EOS) dates directly in the Support Portal UI via “My Dashboard” → Quick links (right hand pane) → Produce lifecycle. Additionally, this information is available via the Tanzu Network replicated API. For example:GET /api/v2/products/{product_slug}/releases/{release_id}- Returns resources including release_date and end_of_support_date
Are there any redirects, how do they work?
The Tanzu Network domain and respective UI will redirect starting on June 24th, 2024.
|
Cutover Date |
Current domain |
Redirected to |
|
June 24th, 2024 |
Tanzu Network |
Customer Support Portal |
The API itself will not have a redirect but will instead cutover to a new service responding to the legacy DNS (network.pivotal.io and network.vmware.com). This is a new DNS - not a http redirect - but the prior API path will continue to work.
Please note that the prior Tanzu Network API is not fully replicated in Support Portal; a subset of functionality has been reduced, but the main endpoints most used for consuming product, release, and slug information has been retained.
IP Addresses to add to Allow List
-
Support Portal - 141.202.0.1
-
Cloudflare IPs
-
-
IPv4- 162.159.140.167, 172.66.0.165
-
IPv6- 2606:4700:7::a5, 2a06:98c1:58::a5
-
Additional domains to add to Allow List as needed
-
downloads2.broadcom.com
-
packages.broadcom.com
-
support.broadcom.com
Emails to add to Allow list
For Support Portal notifications, allow the following: [email protected]
Where can I find API documentation?
Documentation can be found here: https://developer.broadcom.com/xapis/tanzu-api/latest/all-tanzu-apis/
How is the pivnet-resource changing?
The pivnet-resource can continue to be used, however the metadata returned may be limited due to API changes. For example, copy_metadata will operate on less metadata after the cutover.
How does EULA acceptance work?
-
EULA acceptance is not shared between the Support Portal UI and Tanzunet API
-
Acceptance is per user account, per release
-
Tanzunet account users need to re-register in Support Portal for UI-based acceptance.
-
Tanzunet user credentials were migrated to Support Portal if used within the last 12 months
-
Tanzunet accounts will continue to function for API-driven EULA acceptance
API EULA Acceptance Instructions
Option 1
Download the new 7.12.0 OM CLI version from the Github Release, which will automatically accept the EULA for a release when a user requests to download it . The next release of Platform Automation will include this updated version of the OM CLI.Option 2
Use the following `pivnet` cli commands to accept the eula for a given product and release.
pivnet login --api-token=$PIVNET_API_TOKEN
pivnet accept-eula -p $PRODUCT_SLUG -r $VERSION
Option 3
Use curl to manually accept the EULA for a release. Instructions below:
curl -X GET -H "Authorization: $AUTH" "https://network.tanzu.vmware.com/api/v2/products/$product_slug/releases"
- find release w/ the release version number and record the release id
curl -X POST -H "Authorization: $AUTH" "https://network.tanzu.vmware.com/api/v2/products/$product_slug/releases/$release_id/pivnet_resource_eula_acceptance"
How is the OM CLI changing, is there a new pivnet token?
Existing pivnet tokens were migrated if used within the last 12 months. The tokens do not expire.
There is no direct change to OM CLI, it will continue to function. You do not need to download a new version.
Will there be a new Pivnet resource in dockerhub?
No - the existing Dockerhub artifact can continue to be used as-is.
Feedback
