feat: use Azure storage queue to submit bulk-delete tasks
Type of change
-
Bug Fix -
Feature -
Pipeline -
Test -
Documentation
Does this introduce a change in the core logic?
-
No -
Yes
Does this introduce a change in the cloud provider implementation, if so which cloud?
-
AWS -
Anthos -
Azure -
GCP -
IBM
Does this follow conventional commits spec?
-
No -
Yes
Have you set the target Milestone?
-
No -
Yes
Have you set the no-detached-pipeline label?
-
No -
Yes
Updates description?
This MR updates the Azure implementation of the bulk-delete operation to use an Azure Storage Queue instead of a Redis queue to submit deletion jobs and receive them in the Deletion Runner component.