-
Notifications
You must be signed in to change notification settings - Fork 147
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Skip sending step result events for Airlock updates that do not include a status change #2547
Conversation
/help |
🤖 pr-bot 🤖 Hello! You can use the following commands: (in response to this comment from @yuvalyaron) |
/test-extended |
🤖 pr-bot 🤖 🏃 Running extended tests: https://github.com/microsoft/AzureTRE/actions/runs/2994413365 (with refid (in response to this comment from @yuvalyaron) |
🤖 pr-bot 🤖 🏃 Running extended tests: https://github.com/microsoft/AzureTRE/actions/runs/2994413365 (with refid (in response to this comment from @yuvalyaron) |
/test-destroy-env |
Destroying PR test environment (RG: rg-tre63211578)... (run: https://github.com/microsoft/AzureTRE/actions/runs/2996135545) |
PR test environment destroy complete (RG: rg-tre63211578) |
/test-extended |
🤖 pr-bot 🤖 🏃 Running extended tests: https://github.com/microsoft/AzureTRE/actions/runs/2997935124 (with refid (in response to this comment from @yuvalyaron) |
/test-destroy-env |
Destroying PR test environment (RG: rg-tre63211578)... (run: https://github.com/microsoft/AzureTRE/actions/runs/2999449040) |
PR test environment destroy complete (RG: rg-tre63211578) |
/test-extended |
🤖 pr-bot 🤖 🏃 Running extended tests: https://github.com/microsoft/AzureTRE/actions/runs/2999726926 (with refid (in response to this comment from @yuvalyaron) |
/test-destroy-env |
Destroying PR test environment (RG: rg-tre63211578)... (run: https://github.com/microsoft/AzureTRE/actions/runs/3001187006) |
PR test environment destroy complete (RG: rg-tre63211578) |
/test-extended |
🤖 pr-bot 🤖 🏃 Running extended tests: https://github.com/microsoft/AzureTRE/actions/runs/3001737037 (with refid (in response to this comment from @yuvalyaron) |
/test-extended |
🤖 pr-bot 🤖 🏃 Running extended tests: https://github.com/microsoft/AzureTRE/actions/runs/3005766060 (with refid (in response to this comment from @yuvalyaron) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm. minor suggestion
Co-authored-by: Elad Iwanir <13205761+eladiw@users.noreply.github.com>
/test |
🤖 pr-bot 🤖 🏃 Running tests: https://github.com/microsoft/AzureTRE/actions/runs/3007234250 (with refid (in response to this comment from @yuvalyaron) |
/test |
🤖 pr-bot 🤖 🏃 Running tests: https://github.com/microsoft/AzureTRE/actions/runs/3007328448 (with refid (in response to this comment from @yuvalyaron) |
Resolves #2540, #2534
What is being addressed
As part of #2504, Airlock requests might be updated without updating their status (for instance, enumerating the request files adds the files to the request without changing its status), however the method that updates the requests is also responsible for sending
status changed
events, so when there is an update to an Airlock request, a status changed event is triggered, in cases where it was not necessary, such as in file enumeration this resulted in duplicated step results.How is this addressed
update_and_publish_event_airlock_request
, we skip the send of status changed event