How to segregate server folders access per workflow or per collection ?

Hello,

I have workflow(s) which must read some data file(s) directly put on the server.

No problem... but it seems that from a workflow, I can read any file on the server... (and maybe write any file on the server).

How to segregate server folders access per workflow or per collection ?

Regards,

Alex

Server

Accepted answers

All comments

You can do this via worker nodes. and hypothetically files included as workflow dependecies SHOULD (should) be stored in .yxzp files when not running locally. Files written to Server in non-temp directories will be accessible cross Server. Files written to temp directories should (should) be ephemeral and removed at completion of the workflow. AFAIK -> there is no cross file privilege restriction which you can use prevent cross workflow file access. You can segregate jobs/processes by machine/node - which would look down files generated during a process to that process.

Much of this falls on the admin who should be tasked with knowning what the workflows do---> and the users/builders ---> who presumably will not be poking around other directories on the Server/workfer machine. This is a bit of a trust issue.

Quick Links

Tags

This months top contributors

atcodedog05 19458

Qiu 15866

MarqueeCrew 13708

apathetichell 13703