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?
Please sign in to leave a comment.