Allow configuration of Storage Account for Function with Event Hub input binding
Currently, an Azure Function gets one Storage Account, which is configured via the AzureWebJobsStorage property.
This Storage Account is then used for any meta-data that the Function may need to store to work as expected.
In the case of an Event Hub input bound Function, a blob container is created, which tracks the checkpoint of every partition in the Event Hub.
Due to the Storage Account requirements for a Function, it is not possible to take advantage of Premium Storage for the Event Hub checkpointing process.
While it makes sense to require a Storage Account that can support multiple types of storage types as a catch all or default configuration, the user should be allowed to configure specific storage accounts for specific Function bindings.
Your help in allowing this customizability is greatly appreciated.
It would be great to get an a sense for some of the specific features you need from the storage configuration, but this seems like a perfectly reasonable request. There has been some recent exploration of the AzureWebJobsStorage usage, so we’ll look to see how that all lines up with this.