How to deploy an existing flow from sandbox to prod?
The way we deploy from sb to prod is to have a naming convention that carries the flow's version out. For example, "The sample flow V1.0.0". When updating this flow in sb, we clone it and update its version to "The sample flow V1.1.0", make out changes to this cloned version, then clone this with the same name for prod and then update all the connections for the second clone to use all of our prod connections. This approach is working fine, but I can my concern is as the number of our flow as well as the size of our team grow, we will not enjoy this non-standard, mistake-prone manual process. Does Celigo already have a prod deployment process in place that we're not aware of?
-
Hi Bahman Ashtari,
I think you might benefit from using our Integration Lifecycle Management features. This includes creating backups of your integrations, merging changes between an original and clone integration, and even reverting changes if they break your integration.
In relation to your exact question, you might like the recommendations for updating between sandbox and production using Integration Lifecycle Management:
If you have access to the sandbox environment, create an integration in the sandbox first. Then, create a clone in the production environment. When you introduce new changes, make them in the sandbox integration and, once everything is working as expected, pull the newly tested changes into the production integration.
Let me know if this helps out. Thanks!
0 -
Hi Bahman Ashtari,
As Kathyana Queeman mentioned, ILM (Integration Lifecycle Management) is the right solution for you in this situation and what is recommended by us. This works like a versioning control tool and allows you to maintain different versions of the integration within it.
We are also working on adding more features to this feature that benefits. Please let us know if you have any further questions on this.
0
Please sign in to leave a comment.
Comments
2 comments