microsoft / microsoft/AzureTRE
Define available subscriptions in `config.yaml`
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 235
- Forks
- 192
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 13
Description
With the multi-subscription capability enabled by PR #4455, it would be nice to configure available subscriptions when the core is deployed.
PR #4429 also enables array items to be added to config.yaml so this means the list of available subscriptions could be added.
The core deployment could then grant the permissions required to the id-vmss-treid managed identity when it is deployed.
The list of available subscriptions could also be made available via the API which would enable a more friendly drop-down list selection when creating a workspace.
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 by reading PRs #4455 and #4429, then inspect the core deployment and config.yaml handling. Done means the deployment can configure available subscriptions and grant the managed identity required permissions, with that list exposed through the API for workspace creation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, python
- Domain
- api, authorization, cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100