Workflow Manager for Eclipse
Please enter here remarks, questions or feedback regarding the Marketplace listing Workflow Manager for Eclipse https://marketplace.collibra.com/listings/workflow-manager-for-eclipse/
Paulo Taylor
Posted 5 years ago · Edited 1 year ago·Last reply 4 years ago
13 comments
luigicardeles
·4 years ago · EditedHi, do you have any tips for setting up the connection using SSO?
In Workflow Connections, it is mandatory to fill in username and password.
Thanks for any help;
graememathieson
·4 years ago · EditedWe have SSO in our organisation - so regular users are logging in via SSO. However, we have defined one native account on collibra that uses a traditional username/password. This user is used for REST calls and for loading workflows from eclipse. It is an admin account, so it is important to choose a secure password, refresh it regularly and restrict access to people you trust.
Former User
·5 years ago · EditedPaulo, since work is underway on this, my strong recommendation would be a no-code setup. Not every data governance team has enough technical resources for tailoring / developing workflows. That is also true for most of the business organizations who we would like to take a larger hand in defining and deploying their own workflows. Think outside the current box, and make it simpler for data citizens.
Former User
·5 years ago · EditedPaulo, since work is underway on this, my strong recommendation would be a no-code setup. Not every data governance team has enough technical resources for tailoring / developing workflows. That is also true for most of the business organizations who we would like to take a larger hand in defining and deploying their own workflows. Think outside the current box, and make it simpler for data citizens.
noor
·5 years ago · Editedtrue…API development & workflow development make the implementation an IT oriented one…
Paulo Taylor
OP5 years ago · EditedHi @arthur.burkhardt,
When would you be free for a quick call somewhere this week?
arthurburkhardt
·5 years ago · EditedIt’s very cool to have packaged this functionality as an eclipse plugin, but I wanted more functionalities and I ended up writing a python script that I call through the eclipse external tools, which basically provide the same level of integration, but more advanced upload capabilities.
This makes it a joy to work with workflow, in addition to my tips to remove stack traces from the console logs, which facilitate debugging.
Happy to have a call if you’re interested! It would be awesome to see those functionalities into the workflow manager!
arthurburkhardt
·5 years ago · EditedIt’s very cool to have packaged this functionality as an eclipse plugin, but I wanted more functionalities and I ended up writing a python script that I call through the eclipse external tools, which basically provide the same level of integration, but more advanced upload capabilities.
This makes it a joy to work with workflow, in addition to my tips to remove stack traces from the console logs, which facilitate debugging.
Happy to have a call if you’re interested! It would be awesome to see those functionalities into the workflow manager!
scottnichols
·5 years ago · EditedHi Arthur,
Thank you for the feedback. It’s interesting how you’ve written your on development framework to manage the groovy scripts. The workflow manager’s main purpose is to simplify moving files from the Eclipse IDE to the cloud. Your feedback is great for Collibra’s new cloud based workflow design tool that is under development.
–Scott
arthurburkhardt
·5 years ago · EditedSure! For me, the real time saver was to avoid any manual intensive operation for workflow deployment.
No copy/paste
Autocomplete
Autodeployment
Archival
No useless stack trace in the console
graememathieson
·5 years ago · EditedI’ve been asked to post a message here - but I’m already interacting with support team through various channels.
I’m unable to use the workflow manager plugin through a proxy.
I’ve done various tests on two versions:
V0.1.20 not connecting at all.
V0.1.19 is connecting to the server with same credentials as v1.20 but is incompatible with my collibra environment. I am running 2021.02 version of collibra - although some of our servers were rolled back to 2021.01. makes no difference which 2021 version I try to connect to.
I have set up a few tests and I am confident that v1.20 would work without a proxy, but all the tricks I’ve tried from google have come to nothing. We have IP whitelisting on our collibra cloud servers so connecting via a direct connection would not be an option.
arthurburkhardt
·5 years ago · EditedHave you looked into cntlm?
Usually the problem with enterprise proxy is that they use ntlm authentication, which is a problem for many solutions (like the workflow manager). http://cntlm.sourceforge.net/
Basically you use cntlm to deploy a local proxy to interact with your enterprise proxy. This way you can transparently connect through your enterprise proxy without any constraint.
graememathieson
·5 years ago · EditedI did look at creating a local proxy, but it was beginning to look like a lot of work. In this particular case, the proxy we use is a simple http:// forward proxy. It is not authenticating us but we cannot get out to the internet unless we go via the proxy.
In the long term I’d be very interested in the solution you have implemented but I need to weigh this up against the fact that collibra seem to be moving to an online editing option in a future release, so would I just be better to wait for that.
Incidentally I just noticed I replied to the wrong person - meant to reply to the post from @paulo.taylor.
Graeme