microsoft / microsoft/AzureTRE
Delete of in-progress container is triggered twice
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 235
- Forks
- 192
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 13
Description
Describe the bug
When approving/rejecting airlock request the container of in-progress is deleted and then tries to re-delete even though it is already deleted. That occur since the Blob.Created Az Function is triggered on both Blob.Created and Blob.Deleted events (the ip event grid system topic is subscribed to both events).
The solution will be to unregister it from Blob.Deleted events and keep only Blob.Created events.
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
Locate the Blob.Created Azure Function and the ip Event Grid system topic subscription. Confirm where Blob.Created and Blob.Deleted events are registered, then verify that only Blob.Created remains subscribed and the in-progress container is not deleted twice.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, python
- Domain
- backend, cloud
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100