How can I delete a queue from azure function?

Thomas Ligon (Office 365) 26 Reputation points
2022-09-27T15:28:40.707+00:00

I am trying to delete a queue output from my Azure Functions app, but I am getting a message:
Failed to delete HttpHS2 (msgOut): Error creating function. Your app is currently in read only mode. Cannot create or update functions.

The app was created by using the tutorial for creating an http-triggered app, then using the tutorial for adding queue output. Then I learned that my data was too big for a queue, so I added reading from and writing to an Azure file share. Then I added the code that I had already developed on a PC. While working on this I decided to do some cleanup and delete the queue.

In VS Code, I modified function.json and init.py and tested local invocation, which looks good. But, invocation in the cloud fails with an error "request timed out", but I can see that there is a problem behind that.

On the portal, I can find my function app azFunctionHS2, and, under that, the function HttpHS2. Under that, Integration shows that the Azure Queue Storage (msgOut) is still there. When I try to delete it, I get
Failed to delete HttpHS2 (msgOut): Error creating function. Your app is currently in read only mode. Cannot create or update functions.

In VS Code, I successfully modified function.json, but I can also see something called HttpHS2.json, which looks exactly like function.json, but the queue definition is still there. When I try to delete it, I get an error
Cannot edit in read-only editor

Azure Functions
Azure Functions
An Azure service that provides an event-driven serverless compute platform.
4,188 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Thomas Ligon (Office 365) 26 Reputation points
    2022-09-28T16:59:03.017+00:00

    The problem has disappeared, and the function is now running in the cloud. I tried some things that have something to do with the error message, but shouldn't have been applicable to this, and I really don't know why it is OK now. Maybe it was just redeploying the function.

    0 comments No comments