download-artifact | using download-artifact @ v1 , a directory | Computer Vision library

Don't rely on:

Based on the above problem statement, we understood that you are looking to clear the web app cache post the deployment.

In order to achieve this, you can add an app settings WEBSITE_LOCAL_CACHE_OPTION=Always which help you in clearing the local cache of the web app.

for any App Service, its related contents (code files, resources etc.) are being hosted in a Shared Content Folder in order to provision all the features of the App Service like Load Balancing etc. So, if there are 2 VMs configure for Load Balancing then there would just one shared location where all the content of the App Service is hosted.

When these Web Apps refer to the Content Folder, there might be chances of Latency issues (although, Azure takes care of most of these issues) which might slow down the performance of the websites a bit. In such Performance-critical application, we can leverage the features of “Azure App Service Local Cache”.

For more information, you refer to this Azure documentation on Azure App Service Local Cache & this blog post as well .

So yes, I figured out how I can solve this pain.

So all I had to do is create .env file before the build, see the full yml below:

To host static files in your web app, add the whitenoise package to requirements.txt and the configuration for it to settings.py. as mentioned here : Django Tips

requirements.txt | whitenoise==4.1.2

Found the answer on this stackoverflow question: https://stackoverflow.com/a/66929604/14502018

I needed to set the environment that my secrets are stored in. Inside the build job I added this line:

Referring to the error trace this is some configuration issue where we need to set the domain for our webapp. Check for the documentation on how to setup a custom domain in Webapp.

Also as suggested from the comment, we can set default environment variables in GitHub that are available to every step in a workflow run.

Documentations to check the variables.

You can set an env variable exactly as you described at the workflow level.

Just note that it can conflict with env variables set at the job level, or at the step level, if they have the same name. In that case, the variable used is the most specific one: STEP over JOB over WORKFLOW.

Reference 1 + Reference 2

Here is an example of how to use env variables at different levels (without conflict):

Eventually I managed to do this using a custom GitHub Action :