microsoft / microsoft/AzureTRE

deleted template properties are not removed by upgrade process

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

Nobody has claimed this yet.

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

Description

Description

I have noticed that if you remove a property from the template and do an upgrade they are not removed from the workspace or workspace service properties, do we think they should be, or is there a way to do this? I guess in the cosmosDB

Steps

The steps I have tried are:

  1. Deploy a workspace service containing a property such as my_new_property
  2. Remove my_new_property from the template
  3. Upgrade the workspace service
  4. Observe that the property is still present

Code

The code I am using is:

    "my_new_property": {
      "$id": "#/properties/my_new_property",
      "type": "string",
      "title": "my new property",
      "description": "my new property",
      "default": "test property",
      "updateable": true
    }```

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

Reproduce the issue using the listed workspace service deployment, property removal, and upgrade steps, then trace the upgrade process that handles workspace and workspace service properties. Confirm whether the property is retained in Cosmos DB and define done as an upgrade removing properties deleted from the template.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, python
Domain
backend, databases
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
40/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.