feat: make task queues for Azure operations abstract
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
conventional commits spec?
Does this follow-
No -
Yes
Have you set the target Milestone?
-
No -
Yes
Have you set the no-detached-pipeline label?
-
No -
Yes
Updates description?
This abstraction allows to:
- add new task queue technologies by adding more
ITaskQueueWorker
s (e.g. support task queues based on Azure Storage Queue or Service Bus) - subscribe to multiple queues at the same time by just adding more
HostedService
s (e.g. to smoothly migrate from one queue to another) - add new task types to execute by adding more
ITaskExecutor
s (curently we only have Delete operations)