Closed isaacabraham closed 7 years ago
MBrace.Core and by extension MBrace.Flow do not on themselves perform any type of parsing on the paths. This job is delegated to the ICloudFileStore
abstraction that the current runtime happens to be using.
So I think this really is an MBrace.Azure issue: we should consider whether the concrete implementation of ICloudFileStore
, BlobStore
should support multiple storage accounts and recognise WASB-style paths.
If we decide to go for this approach, there are a few ramifications that might be worth considering:
There are quite a few ways we could address these concerns: One would be maintain an "accounts" table in the master storage account which would contain all secondary connection strings. I do feel though that this may violate security expectations users may have.
Another would be to use the service bus to broadcast additional auth data to workers.
See https://github.com/mbraceproject/MBrace.Azure/pull/161 which I think covers this enough for these purposes (an MBrace.Core PR may follow out of that)
There's a need to have the ability to specify the account as part of the path e.g.
etc. etc.
I've raised this as its own issue as it's probably an enabler for a number of scenarios.