Managing the life cycle of a recipe
Learn about how recipe lifecycle management in Reltio Integration Hub helps you move recipes across environments and preserve your customizations during upgrades.
Recipes typically follow a lifecycle that includes creation, testing, and deployment in an environment where the end-to-end integration flow is validated. After a recipe works as designed, you can move it to another environment. For example, create a recipe in a development environment, move it to a test environment, and then promote it to a production environment.
Recipe lifecycle management helps you preserve integration assets during upgrades and environment changes. When you export recipes together with their dependencies, keep package contents in source control, and use recipe version history to review or restore prior changes, you reduce the risk of losing custom work during a deployment or upgrade.
Reltio Integration Hub supports the following lifecycle management capabilities:
- Export and import packages that contain recipes and their dependencies, such as lookup tables and message templates.
- Store packaged recipes in Git for version control.
- Save changes in recipe version history and restore an earlier version when needed.
- Use projects and folders to organize recipes and related assets.
- Include recipe dependencies in an export and import them into a target account.
- Exclude credentials, keys, and other private connection data from exported packages.
For more information about packaging recipes and dependencies for deployment across environments, see Recipe lifecycle management.
Customization behaviour across upgrades and environment changes
Reltio supports only the connector and recipes provided with Reltio Integration Hub (RIH). The following guidelines help preserve customized behavior after upgrades or environment changes:
- Before the upgrade, export the recipes and related assets that you want to preserve.
- If you store packaged recipes in Git, commit the latest package before the upgrade so you have a version to compare or restore.
- Review the recipe version history to identify recent changes or restore an earlier version.
- After the upgrade or import, review customized assets in the target environment.
- Validate that your custom recipes and configurations work as expected.
- Reconfigure any customization that no longer matches the target environment.
Export Manifests and Package Contents
A manifest defines the contents of a package. The manifest identifies which recipes are included and lists their dependencies, such as lookup tables and message templates. When you export a package, it controls what is included and moved to the target environment.
To know more about creating and using an export manifest, see Export: Packaging Recipes and Dependencies.