azureblobstorage: add note about breaking change in 1.25 (#381)

triggermesh · May 25, 2023 · 41a9867 · 41a9867
1 parent 0ed817a
commit 41a9867
Showing 1 changed file with 3 additions and 0 deletions.
diff --git a/docs/sources/azureblobstorage.md b/docs/sources/azureblobstorage.md
@@ -2,6 +2,9 @@
 
 This event source subscribes to blob events from an [Azure Storage Account][storage-acc] through an Event Grid subscription. Events are consumed from a dedicated [Event Hubs instance][eventhubs].
 
+!!! warning "Minor breaking change in 1.25"
+
+    The `AzureBlobStorage` source uses Azure Event Grid under the hood to transport Blob Storage events into TriggerMesh. In `1.25`, the naming convention used to create subscriptions in Azure Event Grid has changed and compatibility is not maintained with the previous naming convention. This means that when updating to `1.25`, we recommend that users of `AzureBlobStorage` source first delete existing components and then create a new ones. This will delete the old Event Grid subscription before creating the new one with the new naming convention. It isn't a big deal if you don't do this, simply know that a new subscription will be created in Azure Event Grid and the old one will linger unused.
 
 With `tmctl`: