GRANT READ and WRITE access to VOLUME

[pohlposition]

UCX will create VOLUMEs to map to various things:

• DBFS Mount Points ([FEATURE]: Create UC External Location, Schema, and Table Grants based on workspace-wide Azure SPN mount points #94)
• s3fs & boto usage (feature: handle s3fs library, s3fs.S3FileSystem calls #443)

Access will need to be granted to these volumes for either READ, WRITE, or both.

It could be as broad as 1 Read Group and 1 Write Group for each workspace and applied to all the mount points in a migrated CATALOG; or something more fine grained.

[HariGS-DB]

@nfx @FastLee
We have mapped storage paths and mounts using spn and instance profile from legacy to external location and added permission for these, we are not migrating these to volumes. Is this issue still required or is there specific cases where we should be creating mounts instead of external location?