Marcel

I want to try out the proposed workaround of @NullMDR but I am to inexperienced to actually apply it properly. Unfortunately the information in the code snippet provided, I don't...

Nevermind the above, it appears I have not read thoroughly enough. The way I see it, you're explicitly defining the kind of storage account (i.e. the way it is created)...

FYI, this is working for Service Bus and Event Hub. Jeff Hollan, principal pm on the azure functions team informed on the reason why this is on twitter https://twitter.com/jeffhollan/status/1260600212617179137

I imagine a workaround could look like this: * blob-triggered function A triggers on new blob in container C * function A pushes the blob-event's meta data via queue message...

Another workaround * go to the hosting storage account's Events section * create a EventGrid subscription, listening for BLOB CREATED events * have these delivered to a queue of your...

Unfortunately not, from the above I think the event grid option is still the ~okayest

I second what @iSeiryu said. Afterall, hot reload was successfully kept in NET6 also for non Visual Studio users. How can this be integrated into the function core tools?

@CharlieDigital how did you get it to work with vs code? Sorry if I misunderstood.

> @mdddev I used @marcin-dardzinski 's workaround as described above in this discussion. Hi @CharlieDigital , thanks for hinting me in that direction. I tried this, however, it seems that...

I am having the same problem, I cannot create a deployment slot off the main app if the app settings is using a key vault reference. I already tried 'allowing...