Follow these practices to keep integration lifecycle management (ILM) workflows predictable, reduce failed pulls, and keep a stable state to return to. Each practice links to the article that explains how to do it.
Protect your integration
- Create a snapshot before you change an integration. Take one before major or minor changes, before you hand an integration to a new user, and before a developer or other technical resource edits it. See Back up an integration with a snapshot.
-
Automate backups. Use the create a snapshot revision endpoint,
POST /v1/integrations/{_id}/revisions/create, or build a flow that creates snapshots weekly or at another interval. The API creates snapshots only. Pulls and reverts require the UI. - Test reverts in a non-production environment before you apply them to production. See Revert changes.
- Review the audit trail. Check who changed an integration, when, and what changed, including ILM activity. See Work with revisions.
Keep pulls clean
- Change only one integration between pulls. Changes to both the original and the clone cause merge failures. See Pull changes from one integration to another.
- Pull small changes often. Large gaps between pulls raise the risk of unexpected Removed and New actions. See Troubleshoot ILM revision and pull issues.
- Use one connection per original connection when you set up a clone. See ILM supported resources and limits.
- Repopulate lookup cache data after every pull and revert. See ILM supported resources and limits.
- Don't clone resources and reuse them inside the same integration. Doing so can cause inconsistencies across revisions. See Clone an integration for Integration Lifecycle Management (ILM).
Work as a team
- Coordinate before you add collaborators, so that people don't change the same integration at the same time.
- Limit who can edit production. Give developers Manage access only to their development integrations. See Developing with integration lifecycle management.
- Separate stages into environments. See Developing with integration lifecycle management.