Articles in this section

Best practices for ILM

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

Work as a team