As I have seen with you Dmitry, today there is a kind of control during workflow execution that prevents anything from running if no connectors are available through "Add/Edit connectors".
For example if you define a repo.sqlite that does not exist and then you try to run a workflow based on file, there is an error message telling you there's no connector and the worflow does not execute. But the workflow does not need any connector so that should not be a blocking control. I was wondering with Dmitry if this control could be disabled :
This is particularly a problem when you want to implement the data catalog with no access on any connectors from the desktop. In this case no connector is available so easymorph workflow fails with that error message. But it should work as in the target users will only use the "retrieve catalog item" which does not need any connector (in this case datasets are computed on server side, not desktop).
Hi team, an old topic still problematic. Imagine you make the catalog available without the possibility for users to use connectors. This is a classic management as users do not need to use connectors for the catalog, everything is hidden.
Problem : with the desktop, if you want to use an action "retreive catalog asset" inside a catalog workspace without connectors access, Easymorph fails. Easymorph always need a connector repo whatever happens, even if the only action in the project does not use connectors, like retreive catalog asset. Even if it's just a list creation. This is not really coherent. The error message is "Error: Connectors can't be loaded: Getting a list of shared connectors for current space is forbidden." There should be a kind of dependency with action : this action requires connectors, this action does not. and when one requires connection, ok you can display the message.
