microsoft / microsoft/AzureTRE
Name of Airlock Notifier subnet is misspelled
Open
Nobody has claimed this yet.
breaking-change
bug
bundles
- Dominant language
- Python
- Stars
- 235
- Forks
- 192
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 13
Description
Remember to label the issue with the appropriate area, and also assign it to yourself if you plan to work on the issue in the near future.
Describe the bug
The airlock notifier's subnet in the core vnet is misspelled as AirlockNotifiactionSubnet.
Steps to reproduce
- Deploy airlock notifier.
Azure TRE release version (e.g. v0.14.0 or main): v0.17.0
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 searching the repository for AirlockNotifiactionSubnet and inspect the core vnet configuration used when deploying the airlock notifier. Correct the subnet label and verify that an airlock notifier deployment uses the corrected name.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100