SKP Catalog/Quality - use REST API to read and create Asset Versions

As Data Quality is now more widely used, some customers will deploy it with multiple tenants of SKP. This poses a problem when trying to move the Catalog Asset Versions. For Eli Lilly, the chief concern is that asset version history will be lost when moving from their SKPv1 tenant to their SKPv2 tenant, but the same issue exists if they should ever need to move to some “v3” tenant in the future. It is considered a high risk at Eli Lilly that they cannot move Asset Versions between tenants.

Please enhance the SKP REST API to include a Version parameter when reading or creating the various Catalog assets that permit versioning. The current design always returns the latest version and there is no method for creating multiple versions of an Asset at once.

SKPv2 REST API