Overview

This article describes the procedure for migrating your existing REST pipelines and accounts to the HTTP Client Snap and accounts. Refer to this example pipeline for migrating the REST pipeline and account.

Prerequisites

• Valid access to the Org and Project space.
• Optional. Identify the number of REST pipelines and accounts to be migrated. You can use the Scan pipeline to scan the project paths where the REST pipelines are located.
• Save a version of the pipelines containing the REST Snaps. You can use the automated Version creation pipeline to create a version of the given pipeline, if the Action type is update.
• If you need to update the existing pipelines, set the Action type to update in your migration pipeline configuration.
• If you need to create new pipelines and accounts, set the Action type to create in your migration pipeline configuration.
• Also, create a new project and copy the assets, such as files, to the same project folder.

Understanding the Migration Tool

The migration tool includes the following pipelines:

• Scan pipeline: This pipeline scans the specified project path for all the available REST pipelines and accounts and provides both lists.
• Version creation pipeline: This pipeline automatically creates versions for all the REST pipelines in a given project. Hence, we recommend that you use this pipeline if you want to update your existing pipelines because it assists you in the migration process by creating backup versions of the affected pipelines.
• Child pipelines: Includes the following pipelines for migrating REST accounts and pipelines:
  • Account migration: REST to HTTP Client Account migration
  • Pipeline migration: REST to HTTP Client Pipeline migration
• Parent pipeline: This pipeline runs the child pipelines to migrate REST pipelines and accounts in bulk to the HTTP Client.