Create and pull changes from one integration to another

To create changes, you simply have to clone your integration and make changes to either your remote or current integration. You can make changes to exports, imports, connections, scripts, or flows. Just remember, cloning is done at the integration level, not the flow level. You can't clone one flow; you have to clone the entire integration. This doesn't mean that you can't change a flow. It just means that if you want to manage or test a flow using Integration Lifecycle Management, you must clone the entire integration.

Contents

• Learn about Integration Lifecycle Management
• Manage integration lifecycles
  • Back up an integration with a snapshot
  • Clone an integration
  •  Create and pull changes from one integration to another
    • Create changes
    • Pull changes
  • Review changes within a pull or revert
  • Merge changes within a pull
  • Revert changes

Note: You can revert to an integration state within a completed pull revision in your revision history at any time.

Pull changes

Pulling or fetching changes lets you compare one directly related integration to another. You can pull data only from a direct clone or source integration. For example, clone your Original integration into Clone A, then A to B, B to C, and B to D. You can create a pull between integrations A and B, B and C, B and D; but not between A and C, or C and D.

Important: You can't make changes to both related integrations (Original and Clone A) and merge your changes. If you make changes to both, your future merge will fail. Only make changes to one integration at a time.

Imagine that you changed an integration and need to pull the changes into your clone. The process is fairly straightforward:

1. Navigate to your original integration and create a pull.
2. Click Revisions → Create Pull to begin pulling changes from the remote integration to your current integration.
3. Add a description of your pull and select your integration from the list. You can pull your clones into your integration one at a time in any order.

4. Review changes between your original and clone integrations. They can sometimes include new resources like exports, imports, and scripts.
   1. You may have conflicts if you made changes to each clone individually. Review and fix any outstanding issues before completing your pull to resolve your conflicts.
5. Click Next to approve and merge the changes. You can review your pull at any time in the Revisions tab.

Example: Update daisy-chained clones

In this example, you are pulling from a Development (Dev) clone, Quality Assurance (QA) clone, and Dev+QA clone to update your original integration. Your clones are daisy-chained, meaning that the Dev+QA clone is created from the original integration, the QA clone is created from the Dev+QA clone, and the Dev clone is created from the QA clone.

After you’ve tested your changes in the Dev clone, pull to QA and then Dev+QA. You may run into similar merge conflicts since your clones should be identical.