My Storage Event trigger is correctly triggered when I upload a file using Microsoft Azure Storage Explorer.
However, the trigger is not triggered at all when using sFTP to upload the same file.
I came to the conclusion that a different value is present for data.api when the file's uploaded using sFTP: SftpCommit
Using Azure Portal, I can easily (manually) add this value to the current list of filtered API's for the created System Topic Event Subscription as seen in the screenshot below.
Issue 1: I believe SftpCommit should be automatically added by Data Factory when creating the Event Subscription, or at least have an option to manually add it using the Data Factory UI or through JSON.
Issue 2: The manual updates I made to the Event Subscription are erased every time I deploy the Data Factory through our DTAP using DevOps since there is no way to add the SftpCommit value to the advanced filter using the Data Factory UI/JSON.
cog-adf
commented
1 year ago
My Storage Event trigger is correctly triggered when I upload a file using Microsoft Azure Storage Explorer. However, the trigger is not triggered at all when using sFTP to upload the same file.
I came to the conclusion that a different value is present for data.api when the file's uploaded using sFTP: SftpCommit Using Azure Portal, I can easily (manually) add this value to the current list of filtered API's for the created System Topic Event Subscription as seen in the screenshot below.
Issue 1: I believe SftpCommit should be automatically added by Data Factory when creating the Event Subscription, or at least have an option to manually add it using the Data Factory UI or through JSON.
Issue 2: The manual updates I made to the Event Subscription are erased every time I deploy the Data Factory through our DTAP using DevOps since there is no way to add the SftpCommit value to the advanced filter using the Data Factory UI/JSON.