Airlock processor handles request Submission

[eladiw]

Fixes #1836

What is being addressed

Adding support for the StatusChangedEvent in the Airlock processor (for submission - import and export)
Consolidated the blob created queues into a single SB topic
Wired all TF scripts
Added support for the blobCreatedEvent in the AL processor

How is this addressed

• Added code to extract the msg from the status changed queue
• If data copy is required, extract the source and dest params, and issue a copy command
• added unit tests

How to test:

1. Create container in the import external storage. Give it a name: e.g. 123
2. Put a single file
3. Place this message in the status_changed queue

{ "data": {
"request_id" : "123",
"type":"import",
"status":"submitted" ,
"workspace_id":"124"
}
}

Check the in progress storage account , it should contain a new container with the same file.
Check the step result queue, you should find a step result event which states the request is now in-progress (transitioned from submitted)

[eladiw]

/test

[github-actions]

🤖 pr-bot 🤖

🏃 Running tests: https://github.com/microsoft/AzureTRE/actions/runs/2466146573 (with refid 3de19bb9)

(in response to this comment from @eladiw)

[damoodamoo]

I'm missing lots of airlock context, but done my best to review.

My main concern would be using any blob triggers to determine stage transitions - as this will pretty much pin us to one file and require a lot of refactoring if we wanted to support multiple in future.

[eladiw]

@damoodamoo @tamirkamara fixed all comments

[tamirkamara]

Added a couple of small comments. Up to you...

[eladiw]

/test-extended

[github-actions]

🤖 pr-bot 🤖

🏃 Running extended tests: https://github.com/microsoft/AzureTRE/actions/runs/2492978719 (with refid 3de19bb9)

(in response to this comment from @eladiw)

[eladiw]

/test

[github-actions]

🤖 pr-bot 🤖

🏃 Running tests: https://github.com/microsoft/AzureTRE/actions/runs/2493332545 (with refid 3de19bb9)

(in response to this comment from @eladiw)

[eladiw]

/destroy-test-env

[github-actions]

🤖 pr-bot 🤖

/destroy-test-env is not recognised as a valid command.

You can use the following commands:
    /test - build, deploy and run smoke tests on a PR
    /test-extended - build, deploy and run smoke & extended tests on a PR
    /test-shared-services - test the deployment of shared services on a PR build
    /test-force-approve - force approval of the PR tests (i.e. skip the deployment checks)
    /test-destroy-env - delete the validation environment for a PR (e.g. to enable testing a deployment from a clean start after previous tests)
    /help - show this help

(in response to this comment from @eladiw)

[eladiw]

/test-destroy-env

[github-actions]

Destroying PR test environment (RG: rg-tre3de19bb9)... (run: https://github.com/microsoft/AzureTRE/actions/runs/2493701571)

[github-actions]

PR test environment destroy complete (RG: rg-tre3de19bb9)

[eladiw]

/test-extended

[github-actions]

🤖 pr-bot 🤖

🏃 Running extended tests: https://github.com/microsoft/AzureTRE/actions/runs/2493857357 (with refid 3de19bb9)

(in response to this comment from @eladiw)

[eladiw]

/test-extended

[github-actions]

🤖 pr-bot 🤖

🏃 Running extended tests: https://github.com/microsoft/AzureTRE/actions/runs/2494018111 (with refid 3de19bb9)

(in response to this comment from @eladiw)

[eladiw]

/test

[github-actions]

🤖 pr-bot 🤖

🏃 Running tests: https://github.com/microsoft/AzureTRE/actions/runs/2494112493 (with refid 3de19bb9)

(in response to this comment from @eladiw)

[eladiw]

/test-extended

[github-actions]

🤖 pr-bot 🤖

🏃 Running extended tests: https://github.com/microsoft/AzureTRE/actions/runs/2494217775 (with refid 3de19bb9)

(in response to this comment from @eladiw)