Integration Lifecycle Management features help you build and manage your integration’s software development lifecycle by supporting version control, release management, and git-style features to push, merge and commit changes.
You can consider these guidelines when planning your integration management.
- Build or update an integration, preferably in sandbox environment.
- Create a clone to test changes to an integration in a sandbox environment. If you don’t require or have a sandbox environment, create a clone in the production environment. Note that when developing large features that have different teams using different development/testing clones, it’s good to establish guidelines for pulling and merging changes so that teams work well together.
- Create snapshots as a backup. For example, when you have to fix a critical bug quickly, you might want to build and test the fix on the integration in the production environment itself. Snapshots help you to quickly revert to a stable state if you run into an issue.
- Create a clear access policy for effective collaboration.
Here are some examples of approaches and workflows to set up and manage your integration.
Create backups
- Create an integration and manage access level.
- Create a snapshot.
- Always take snapshots before making changes to critical integrations or set an automated backup frequency using the APIs.
- Audit revision changes when required.
Collaborative development to manage integration changes
- Create an integration and manage access level.
- Create a clone.
- Make changes in one of the integrations.
- Create a pull.
- Review changes with the difference (diff) screen.
- Merge changes.
- Audit revision changes when required.