Hi,
We have a common Error Handler pipeline which we are developing for use across all projects. When I create a new version of the Error Handler, I don’t want to just update it directly in our DEV environment as other developers will be inconvenienced if it breaks their pipelines.
I can create a separate copy (e.g. “Error Handler New”) and then ask each project to migrate across to it - however then we end up with all projects pointing at “Error Handler New” and there is no easy way to rename this back to “Error Handler” without asking every project to repoint their pipelines again.
We could just incrementally name the common pipelines (e.g. “Error Handler v1”, “…v2”, “…v3”, etc.) however we’d prefer not to as we’d rather manage versions in our source code repository, not in Snaplogic.
Any suggestions of how to better manage the introduction of new versions of common pipelines?
Thanks,
C.J.
