Practicing lifecycle management

When can I use lifecycle management?

Imagine that you have a critical business process running in production. A team member introduces new changes that break the integration. Is there a way to go back to a stable state? Is there a better way to test and roll out new changes? And is there a better way to organize integration development across teams and environments?

Use Integration Lifecycle Management (ILM) to manage the lifecycle of your custom integrations from development to test to production. If you introduce new changes in one integration, you can review the changes, control how you roll them out to their clones, and go back to any previous stable state if you run into issues.

Tip: ILM can be used for any custom integration that you create or any template that you install.

You can set up your ILM workflows in many ways based on your internal processes or change management process. The ILM feature is accessible under the Revisions tab in a custom integration tile. The feature is available at the integration level for all the objects within the integration.

Audit integration and revision changes

You have detailed audit logs in integrator.io. You can identify who made changes to an integration, when changes were made, and what those changes were. You can identify the same for integration life cycle management activities.

Backup integrations when new changes introduced

An easy way to implement new ILM practices is by creating backups before making changes. You can use this to roll back to an earlier stable state if you run into integration issues.

Use snapshots to backup your integrations. Create a snapshot when:

• Making major (or minor) changes to your integration
• Handing off your integration to a new user
• Your developer or other technical resource is going to edit your integration

You can also use the revisions API endpoint to automate the backup process or set up a flow to create snapshots once a week or at any desired frequency.

Tip: Snapshots are created automatically whenever you create a pull to merge new changes or revert your revision to an earlier version.