WebApp:`az webapp up` by default resets the Python version to 3.7

Describe the bug

When running az webapp up without the “runtime” flag, the Python version of my webapp is always reset to 3.7, although my Python app is running in Python 3.8. While az webapp up does store other default values from the first deployment in the config file, it does not do so with the runtime version.

Command Name az webapp up

To Reproduce:

• Put any pre-requisite steps here…
• az webapp up --runtime "PYTHON|3.8 --other-args"
• az webapp up

Expected Behavior

Running az webapp up with a new flag should always store that setting as a standard in the config file. This should include the runtime, Python version etc.

Environment Summary

Linux-5.4.72-microsoft-standard-WSL2-x86_64-with-debian-bullseye-sid
Python 3.6.10
Installer: DEB

azure-cli 2.18.0

Extensions:
db-up 0.2.0

Additional Context

[Kotasudhakarreddy]

Looking in to it.

[Kotasudhakarreddy]

Hey @Kotasudhakarreddy , thank you very much for your answer! This does explain why the command acts as it does. However, wenn az webapp up is used to redeploy, it does seem to update the existing app. After all:

1. During the deployment it does say Updating runtime from Python 3.8 to Python 3.7
2. Previously set environment variables on the webapp are kept and not deleted.
3. In this tutorial in the MS Docs it literally says this:

   This command uses the parameters cached in the .azure/config file. Because App Service detects that the app already exists, it just redeploys the code.

Hi @larsschellhas - agreed on your points. Thanks for correcting me. Parameters cached under .azure/config will just store the info related to the azure configuration of your app like RG, SKU etc. Regarding -runtime as per the implementation if we don’t specify the -runtime by default it consider and set as python|3.7. we will look in to the feasibility of considering the runtime version from previous deployment and set as default if we don’t specify in the latest deployment.