@GregorShear

Data Plane Selection & Storage Mappings UI Redesign

Problem

Customers lack visibility and control over storage mappings configuration:

• No UI option for Azure Blob Storage (despite backend support)
• Cannot create subprefix storage mappings (e.g., tenant/eu/) without contacting support
• Cannot select which data planes are associated with a storage mapping
• No way to see or set which data plane is the default
• Array ordering determines the default, which isn't communicated to users

Solution

Replace the current admin view with a clearer interface showing the relationship between storage mappings and data planes.

Mockup: https://estuary-ui.vercel.app/data-planes

Image Image

Key Features

• Hierarchical Storage Mapping View — Display mappings grouped by tenant prefix with provider, bucket, region, and status.
• Storage Mapping Configuration Modal — Edit mapping details, select default data plane from dropdown, guide users toward data planes in this preferred order: private > same region > everything else
• Verify fragment store authorization — Help users add dataplane service creds to their gs/s3 accounts and test connection right from the UI. Block until connections are verified.

Requirements

Continue development in gql api to support this feature:

Mutations

• createStorageMapping - prevent creating new storage mappings that would impact existing specs
• updateStorageMapping - still need to understand how to handle republishing specs (and potential failures).

Queries

• prefixes - consider extending prefix query to return a list of all prefixes/subprefixes, and associated specs - would need something like this for autocomplete prefix fields in the UI, and letting the user know they can't create a new storage mapping because of existing specs

References

• PRD: Data Plane Selection & Storage Mappings Mk2