microsoft / microsoft/AzureTRE

Pushing data into workspaces from external data stores

Open
#4,312 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

question
Dominant language
Python
Stars
235
Forks
192
Avg merge
1d 23h
Merged PRs (30d)
13

Description

We frequently want to push data into a workspace at the beginning of a project, and sometimes to refresh that data later on, possibly on a regular basis. We're currently doing that with a private endpoint in the workspace that connects to an external ADF instance, allowing us to push CSV and (soon) SQL tables too.

We also need to be able to push other data types eventually, such as large amounts of image data, which will go either to shared storage or to a storage account made accessible from inside the workspace.

I'm aware that other people have other implementations. E.g., @jonnyry has his ADF inside the TRE, IIRC, and pushes from there to the client workspaces. That will probably look similar to ours, but not completely.

Can we have a discussion here to see what the requirements are, what work is planned or done, how we might be able to standardise a solution for connectivity to external data stores? Is anyone else doing anything in this space?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by comparing the existing private workspace endpoint and the alternative ADF-inside-the-TRE approach described in the issue. Gather requirements for CSV, SQL tables, image data, shared storage, and regular refreshes, then document an agreed standard for connectivity and confirm the planned work or implementation path.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, sql
Domain
cloud, data-engineering
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.