microsoft / microsoft/AzureTRE

Airlock Notifier deploys with error

Open
#3,917 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
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:

  1. The trigger at the start of the workflow shows an error reading properties, see screenshot below.
  2. 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

  1. Deploy an Airlock Notifier shared service
  2. Go into the Azure portal, find the resource group, then the logic app, and explore the design view for the first error.
  3. 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

Screenshot 2024-05-01 at 6 41 57 PM Screenshot 2024-05-01 at 6 48 44 PM

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

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.