You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The command-line arguments that the language worker receives from the Functions Host have generic names (such as 'host' and 'port'). This can cause conflicts with other environment variables in certain environments. To address this issue, the Functions Host will now send a new set of arguments prefixed with functions-<argumentname>. This will be in addition to the existing arguments.
With the new planned host change, host code will send command line arguments like below.
Initial sanity testing showed that python worker fails to start when the new arguments are sent. We need to fix the python worker to handle these new arguments.
Expected behavior with the fix:
Use the new arguments (the one with "functions-" prefix).
If the new arguments are not present, use the old ones (PORT, HOST etc..)
For any language workers which are consumed as a NuGet package to host, we do not necessarily need the fallback code (using the old arguments). This is because the next host version which will consume the language worker package, will be always sending the new arguments.
The command-line arguments that the language worker receives from the Functions Host have generic names (such as 'host' and 'port'). This can cause conflicts with other environment variables in certain environments. To address this issue, the Functions Host will now send a new set of arguments prefixed with
functions-<argumentname>
. This will be in addition to the existing arguments.With the new planned host change, host code will send command line arguments like below.
The new arguments sent are:
Initial sanity testing showed that python worker fails to start when the new arguments are sent. We need to fix the python worker to handle these new arguments.
Expected behavior with the fix:
See Azure/azure-functions-host#9504 for more details.
The text was updated successfully, but these errors were encountered: