After upgrading some function apps from .NET 6 in process to .NET 8 isolated model that were using blob triggers, it was observed that old blobs that has already been processed were being reprocessed.
After doing some investigation, the culprit is that the path where receipts are kept have changed.
It used the be the namespace plus the name of the method e.g. MyNamespace.Run
however after upgrading its has been change to Host.Functions.\
I cant find any mention of this change or any warning about it. Is this intentional? Is there a known migration path to prevent reprocessing of blobs when upgrading?
Steps to reproduce
create .net 6 in process function app with blob trigger function
deploy to azure
trigger function by uploading some blobs
upgrade to .net 8 isolated model
previously processed blobs will reprocess
Description
After upgrading some function apps from .NET 6 in process to .NET 8 isolated model that were using blob triggers, it was observed that old blobs that has already been processed were being reprocessed.
After doing some investigation, the culprit is that the path where receipts are kept have changed. It used the be the namespace plus the name of the method e.g. MyNamespace.Run however after upgrading its has been change to Host.Functions.\
I cant find any mention of this change or any warning about it. Is this intentional? Is there a known migration path to prevent reprocessing of blobs when upgrading?
Steps to reproduce
create .net 6 in process function app with blob trigger function deploy to azure trigger function by uploading some blobs upgrade to .net 8 isolated model previously processed blobs will reprocess