Defaulting to Identity-Based data access breaks cross-region compute jobs
peterhessey opened this issue · 0 comments
peterhessey commented
It seems that if identity-based access is not available, the v2 API does not fall back to using account keys / SAS tokens. As such, when the submission fails to cross-region compute because of identity-based access not working, then the whole job fails instead of defaulting to account keys / SAS tokens.
A flag should be added to make the identity-based access an opt-in feature, instead defaulting to account keys / SAS tokens still.