Which services to restart when updating custom operations


#1

When in the code/compile/deply/test cycle with a custom operation via the seahorse-sdk, which services should be restarted to ensure the changes get propagated? Right now I do a docker-compose down && docker-compose up, but that takes a while and I suspect it’s overkill.


#2

Restarting the whole Seahorse is always recommended. After running "docker restart seahorse_sessionmanager_1 seahorse_workflowmanager_1 " custom operations appear properly in operation menu. It doesn’t save time because services have to initialize and resend the application to cluster via ‘start editing’ button.


#3

Thanks! Very helpful!