Pipeline migrate/copy with versions as well
When I am copying the pipeline from one project to another, the version information on the source project is not available in the target project space for the same pipeline. What is the best to way to copy/migrate the pipeline with version information as well.1.3KViews0likes0CommentsMigrate Pipelines
Hi Community, I’m trying to build a pipeline that migrate pipelines, accounts, tasks from one Org to another. I constantly receive an error message for the SnapLogic Create snap, while creating the pipeline in an folder. Could you please help me on this part. Error: Failure: Exception creating pipeline %s, Reason: Snapi request failed: {“response_map”: {“error_list”: [{“message”: “‘snap_map’”}]}, “http_status_code”: 500} $target_path: org/project_space/new_project/pipeline ; which will be given as input to the asset path from the above snap.Solved6.4KViews0likes6CommentsMigrate projects, pipelines, accounts, tasks across environments
One of the common requests from customers is how to move Snaplogic asset (pipelines, accounts and tasks) in a project from one environment to another easily as part of the configuration management or promotion processes. The standard project export/import function will move the pipeline, tasks, files, etc., but the customer will need to re-create the account objects and re-link all the account references in the target environment. This extra step could be a hassle if you have a big project with many pipelines and snaps require account references. The sample pipeline here use Snaplogic Metadata Snapack to read the asset definition from a project and write to the target location (same org or not). It will move the accounts, pipelines and tasks from source to target. More importantly, it will maintain the account references in the pipeline and pipeline reference in the task. User just need to re-enter the Account password and re-select the Task snaplex in the target environment. The attached project export contains 4 pipelines: 01 Main - Migrate Project: This is the main pipeline which will call into the following in sequence to move the assets. 02 Upsert Account - This pipeline will move the Account object in a project to the target location. 03 Upsert Pipeline - This pipeline will move the Pipelines in a project to the target location. 04 Upsert Task - This pipeline will move the Tasks object in a project to the target location. User can specify the source and target location (org + space + project) in the pipeline parameters. To run the pipeline to move project across org, the user account will need to have read/write permission to both source and target location. The project export of those pipelines can be downloaded here: Migrate Project v2.zip (10.7 KB)11KViews4likes13CommentsORG to ORG Project Migration Pipeline
Please find attached pipeline to Migrate Account, Pipelines, Tasks from one ORG to another in the same pod. Configurations Change the source and destination org in the pipeline parameter Change the source and destination project name. Note : All the values provided in pipeline parameters are case senstive. ORG_create_account_file_pipeline_task_Migration_2017_02_02.slp (22.0 KB)2.5KViews0likes0Comments