Azure Data Factory, ADF, is a software as a service offering from Microsoft that allows for moving data from one place to another.
It is an 11 year old product and dear reader, I just do not enjoy using it. If it solves your needs, then great, continue using it.
I just have this uncanny knack for wanting to something that is not intuitive to the tool.
In today's edition, I needed to trigger a run that wasn't on a schedule. As we started to go down the route of using the management API, which looks the easiest because it's just a POST. Oh, except now we need to deal with Entra and registering app and stuff to get secrets. Hmmmm, what if we go a different route. We can try these File triggers and have the source process dump a sentinel file when it's ready.
Easy peasy, lemon squeezy. Oh, except no. Azure Storage Account is 4 entities - Containers, File Share, Tables and Queues. Cheap, easy and already in use as the data is going to the Containers. Except, a File Trigger is not a file trigger. Directly at least. Instead, you need to first create an Azure Event Grid (a queuing technology) and then you can associate the file trigger with that.
But why? You have a queue built into the storage account, why not use that?
Anyways, ADF makes me angry for all the silly little crap that should not be a thing and yet, where I am yelling at clouds.