I’m putting together a simple utility subgraph that will be used by jobflows/graphs in multiple sandboxes on our server, accessing files from within those sandboxes. (It’s a tool for uploading to our secure document store, which several distinct projects will use.) What’s the least-redundant way to set this up? As far as I can tell, my options are:
-
Put the subgraph in its own sandbox, and have the jobflows/graphs run it using a path to that external sandbox (e.g. “sandbox://${SANDBOX_NAME}/graph/subgraph/subgraph_name.sgrf”. In this case, I’d have to figure out how to pass fully resolved file paths into the subgraph, since normal relative paths (e.g. “${PROJECT}/foo”) would differ between the source sandbox and the sandbox that’s running the shared subgraph.
-
Put redundant copies of the subgraph and its associated files (a custom Java transformation and some .jars) in each sandbox that will use it. This would eliminate pathing issues, and I think we could reduce the possibility for confusion by keeping it versioned as its own GitHub project and deploying it simultaneously to all sandboxes when updates are made, but still I think it’d be silly-looking.
My preference of course is option 1) but I wonder if there are any gotchas or other quirks I should know about, since it doesn’t seem very commonplace for sandbox assets to interact with external sandboxes. Thanks in advance!