microsoft / microsoft/AzureTRE
Enhance Bundle Registration Process
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 235
- Forks
- 192
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 13
Description
Description
As a TRE System Integrator
I want to specify the full repository where a bundle is stored
So that I can store templates in different locations
As a TRE System Integrator
I want the bundle to be read and imported without the need to manually generate a payload and call the API.
So that I can quickly register new bundles
Acceptance criteria
- Post/register template operations accepts and stores a
repository - Post/register template operation extracts template details using resource processor and stores template details
- Get Workspace Template returns the
repository - Post Workspace with successfully deploys the workspace
Notes:
Docker calls the combination of [registry-url]/[namespace]/[image] a repository. For example https://myregistry.azurecr.io/workspaces/azureml
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the post/register template operation and follow its resource processor, then inspect the Get Workspace Template and Post Workspace flows. Trace how the full Docker repository is accepted, stored, returned, and used for import; done means all four acceptance criteria pass, including successful workspace deployment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, docker, python
- Domain
- backend-api-design, cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100