Migration Patterns

The following patterns migrate assets from one project to another in the same org. These patterns make use of the SnapLogic Metadata Snaps.

Source: Existing accounts, files, and pipelines within SnapLogic
Target: A second project within SnapLogic
Snaps used: SnapLogic Metadata Snaps, Mapper,

Requirements

  • You must have access to both projects.
  • You will need to define the following pipeline parameters:
    • source_path, in the form of /orgname/projectspace/project
    • target_path, in the form of /orgname/projectspace/project

Migrate Accounts

Migrate%20Accounts

  • The SnapLogic List Snap gathers the list of accounts in the specified source_path parameter.
  • The SnapLogic Read Snap reads the incoming $path for the accounts.
  • The Mapper Snap maps the target path.
  • The SnapLogic Create Snap writes the accounts to the target location.

Migrate Files

Migrate%20Files

  • The SnapLogic List Snap gathers the list of files in the specified source_path parameter.
  • The Mapper Snap maps the source path to a $source_path field for use in the Read Snap.
  • The SnapLogic Read Snap reads the incoming $path for the files.
  • The SnapLogic Create Snap writes the files to the target location.

Migrate Pipelines

Migrate%20Pipelines

  • The SnapLogic List Snap gathers the list of pipelines in the specified source_path parameter.
  • The SnapLogic Read Snap reads the incoming $path for the pipelines.
  • The Mapper Snap maps the target path.
  • The SnapLogic Create Snap writes the pipelines to the target location.

Pipeline Downloads

2 Likes

How can we migrate files between orgs without using the Migrate function on the project in Manager? I have tried various methods to read/delete/browse/write files in the source and target orgs with and without accounts that have full access to the source and target orgs. But the files can only be seen by snaps and in Manager when the snap that creates or reads them is executed in the same org. The files can be successfully written by the source org into the target org but snaps executing in the target org cannot see them and vice versa. (Permissions cannot be set on SLDB files by the File Writer snap.) Nothing is working unless I create separate pipelines and tasks for each function (Directory Browser, File Writer) on the target org and call those from the source org with the Rest POST snap so that they are executed on the target org. This seems extremely complicated for a seemingly simple task of deploying files. What am I missing?

Thanks so much @dmiller.

We’re also interested in the following patterns:

  • a migration pattern that would copy over tasks from a source project to a target project and additionally replace the bearer tokens on the copied tasks with a new randomly generated bearer token.
  • a pattern demonstrating how to create a user-specified project or project space.

Thanks!

@omair, I’m asking Dev about the first request to see if it’s possible.

Regarding creating a user-specified project or project space, do you mean a project other than the project created when the user is first created?