How can I upgrade pip (Local Git, App Service) to a specific version and then make the Oryx use that pip?

I am unable to find a clear answer on this.

I thought this would be clear-cut described at least somewhere (no jargon, just plain logic). As a customer, I do not care about your nomenclatures.

I have read a number of articles without no success so far. I scavenged probably 20 different articles all over the place. They either do not apply or there is lack of parity with who is seeing what in their portal.

Things I have read about:

• Using environment variables in the form App Settings [ does not work as it does not appear to apply to the pip that Oryx ultimately ends up using ]
• Using .deployment file with a mention of build.cmd (bash file) to upgrade pip [ does not appear to work due to the same reason ]

All I want is properly bootstrap my application. I believe, in this case, that would mean to make sure the pip is upgraded, and Oryx subsequently uses that pip to install dependencies via requirements.txt; instead, an older pip is used, and installation fails for certain dependencies.

I do not know what is ideal in this case:

• Figure out a Kudu solution
• Figure out a Oryx solution (I assume this)
• Bypass deployment altogether and just copy the entire structure from the local disk
• Figure out some Docker solution

The fact that Oryx tries to build automatically is great and I want to go by that route.

Platform - Linux
Python - 3.6.15
Required version of pip - 21.3.1

Start by tracing how Oryx builds Python 3.6.15 applications on Linux App Service and which pip instance installs requirements.txt. Check the deployment and build guidance against the reported need for pip 21.3.1; done means providing a clear, reproducible procedure or documenting that the requested setup is unsupported.