V5.x release to support cleanly TimerTrigger with Azure Storage V12

We have been upgrading our WebJobs to use Microsoft.Azure.WebJobs.Extensions.Storage 5.x successfully except for the ones that are using TimerTrigger.

TimerTrigger is only available in Microsoft.Azure.WebJobs.Extensions 4.0.1, which depends on Microsoft.Azure.WebJobs.Host.Storage using Azure Storage 11.x

TimerTrigger is also available in the Microsoft.Azure.WebJobs.Extensions 5.x beta.

Is there any plan to move out of beta for 5.x? If not any time soon, is that beta production ready/safe?

Expected behavior

• No more reference to Microsoft.Azure.WebJobs.Extensions 4.0.1 referencing old Azure Storage SDK
• Cleaner Startup code

builder.ConfigureWebJobs((context, b) =>
              {
                  b.AddAzureStorageQueues();
                  b.AddAzureStorageBlobs();
                  b.AddExecutionContextBinding();
                  b.AddTimersWithStorage();
              })

Actual behavior

• Requires reference to to Microsoft.Azure.WebJobs.Extensions 4.0.1 referencing old Azure Storage SDK causing some confusion
• Cluttered startup code

builder.ConfigureWebJobs((context, b) =>
              {
                  b.AddAzureStorageCoreServices();
                  b.AddAzureStorageQueues();
                  b.AddAzureStorageBlobs();
                  b.AddExecutionContextBinding();
                  b.AddTimers();
              })

Related information

#745 Adding storagev12 ScheduleMonitor implementation cc @karshinlin

[mattchenderson]

I don’t have an exact ETA for this at the moment, but that’s something I’ve been trying to get a bit more clarity on. It hopefully shouldn’t be too far out.

[bhagyshricompany]

@superjulius will update you soon