microsoft / microsoft/AzureTRE
Airlock Notifier deploys with error
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 235
- Forks
- 192
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 13
Description
Describe the bug
The Airlock Notifier shared service deploys with an error, reproducibly. There seem to be two erros:
- The trigger at the start of the workflow shows an error reading properties, see screenshot below.
- In addition to this, the SMTP connector doesn't deploy correctly either. It's visible in the logic app as a connector, but when you click on it to get details, Azure reports that the resource cannot be found. See second screenshot.
Steps to reproduce
- Deploy an Airlock Notifier shared service
- Go into the Azure portal, find the resource group, then the logic app, and explore the design view for the first error.
- Still in the Azure portal, find the connectors view, and click on 'smtp' for the second error.
Azure TRE release version (e.g. v0.14.0 or main):
main
Deployed Azure TRE components - click the (i) in the UI:
UI Version: 0.5.21
API Version: 0.18.5
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 reproducing an Airlock Notifier shared service deployment on main, then inspect the Logic App trigger and SMTP connector in the Azure portal as described. Done means the trigger no longer reports a property-reading error and the SMTP connector is deployed and viewable without Azure reporting the resource is missing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100