microsoft / microsoft/AzureTRE

Documentation request for faster development for workspaces and workspace services

Open
#3,258 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Currently we had the following process for bundle development

We are currently working on workspace and workspace service bundles. All of them needs several resources that needs to be created in Azure.

Our current workflow is the following:

  • Create the workspace service
  • Build, deploy and register services (including uploading the bundles to the container registry)
  • deploying an new workspace or workspace service
  • receiving an error
  • retrieving the error from the cosmos database (if it is an workspace bundle)
  • Adapt the bundle and again to the second step

This is a very time consuming process

Describe the solution you'd like

I would like to use the terraform plan or apply command to test my scripts against the already deployed bundle. So if there raises an error I don't need to do the complete round trip for the next try.

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

No files, tests, or entry points are named. Start by reviewing the current Terraform workflow and the workspace and workspace-service bundle deployment process, including how errors are retrieved from Cosmos DB. Done means defining and implementing a way for terraform plan or apply to test scripts against already deployed bundles without the full deployment round trip.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, terraform
Domain
cloud, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.