(Docker) Container Registry Repository Webhook not updating Functions App

Kevin Villalobos 46 Reputation points
2021-05-19T09:43:21.877+00:00

Brief Summary
My Functions App are not updating when I re-deploy the code via docker image on Azure Container Registry.

Details
I have a docker image repository on Azure Container Registry.

I have a Functions App on which I have several Azure functions deployed. My Functions App has the Continuous Deployment enabled.

I created a webhook on which I selected the scope xxxxxxxxazurefunctions:* in order to update the Functions App every time a new image is uploaded to the repository. On the webhook I put the URI of my Functions App.

97855-webhook.png

When I push a new image to the repository the webhook is triggered (see Figure 2). However, my Function App is not uploaded (see Figure 3).

97766-updatedtag.png

97797-functionsapp.png

Workaround:
I can manually change the image of my Azure Functions. However, I would like this to be done automatically. Is there some that I´m missing?

When I change the tag of my image on Azure Functions (manually via Azure Portal), a new webhook is created associated to the selected tag (see Figure 4). In this case, my Functions App is properly updated with the new image. Maybe have something to do with the webhook's scope?

97818-newwebhook.png

Azure Container Registry
Azure Container Registry
An Azure service that provides a registry of Docker and Open Container Initiative images.
461 questions
Azure Functions
Azure Functions
An Azure service that provides an event-driven serverless compute platform.
5,108 questions
0 comments
Accepted answer
  1. Pramod Valavala 20,636 Reputation points Microsoft Employee
    2021-05-20T06:00:40.59+00:00

    @Kevin Villalobos The current container is updated when a new container is pushed for the same tag. For example, if the selected tag is latest and you upload a new container with this tag, only then will it be updated.

    But in production, using latest isn't really recommended and you should use versioned tags (like you already have) and then use a CI/CD pipeline to update your app service, triggering it to pick the latest.

    The CD feature built into App Service is great when you don't really need a full-fledged CI/CD setup. Though it would still be best to use another tag instead of latest because you could accidently update it if you don't set a tag while building the container.

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.