microsoft / microsoft/AzureTRE
'Service Bus Namespace' Continues Running Even After `$ make tre-stop`
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 235
- Forks
- 192
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 13
Description
Hello team,
Is it expected behavior for the 'Service Bus Namespace' to keep running even after executing the $ make tre-stop command?
This screenshot was captured after running the $ make tre-stop command:
Given that the Premium tier of this service is not inexpensive, is there a way to turn it off or disable it when not needed?
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
The issue names the $ make tre-stop entry point and the Azure “Service Bus Namespace” resource, but no files or tests. Trace what tre-stop does to that namespace and check the resulting Azure resource state. Done means establishing whether continued operation is expected and identifying a supported stop or disable path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100