Upgrading from AMR Beta to AMR GA release

This topic tells you how to upgrade from Tanzu Application Platform v1.6 to Tanzu Application Platform 1.7 or later with Artifact Metadata Repository (AMR) beta enabled. Because AMR is not enabled by default in Tanzu Application Platform v1.6, most users will not encounter this scenario. To upgrade without AMR, see Supply Chain Security Tools - Store - Upgrading.

Known issues and workarounds

Because AMR was in beta in Tanzu Application Platform v1.6, there are breaking changes when upgrading to Tanzu Application Platform 1.7. This section lists all the known issues and workarounds.

Configuration Changes

In the AMR Beta release, most of the AMR configurations are in line with the metadata_store section in values.yaml. To configure a workaround:

1. Remove metadata_store.amr from the values file as seen in this example:

   metadata_store:
     amr:
       deploy: true
       graphql:
       app_service_type: "ClusterIP"
   

2. Remove amr.deploy_observer: true from values.yaml.

3. Remove alias from the amr.observer.location config map, as seen in this example:

   observer:
    location: |
      alias: my-cluster
   

Database changes

In the AMR Beta release, the Alias field was introduced in the Location table. The Alias field was removed from Tanzu Application Platform v1.7. To drop this field from Tanzu Application Platform v1.7:

1. Connect to the PostgreSQL Database.

2. Run the following SQL command:

   ALTER TABLE artifact_locations DROP COLUMN IF EXISTS alias;