Access behind a proxy on self hosted runner

[HediehM]

Someone posted this in discussions 2022 and no one responded. Here is our issue:

We are attempting to deploy code to a storage account from a runner in a self-hosted agent Mere the ENV values for the ACA Image are predefined.
When we deploy via a custom bash/python script setting the HTTP_ PROXY, NO_ PROXY, and HTTPS_ PROXY values we are able to connect to our storage account just fine.
However when running the

Azure/functions-action@vl it doesn't appear that the environment variables are being respected:

• name: Run Azure Functions Action
  uses: Azure/functions-action@v1
  id: deploy-to-function-app with:
  app-name: ${( env. AZURE_FUNCTIONAPP_NAME }} package: $ff enAZURE_FUNCTIONARRPACKAGE PATH }}
  env:
  NO_PROXY: "‹internal destination>"
  HTTP_PROXY: "*
  HTTPS_PROXY: ""

I can see in the logs that it reads the proper set values, but somehow the function action is still picking up the value set within the self-hosted runner.

[im-samz]

Hey @HediehM, I'm not aware that the action considers those envrionment variables (HTTP_PROXY, NO_PROXY, 'HTTPS_PROXY`) when deploying. Can you refer me to some docs that describe what you are expecting?

[patelchandni]

This function action does not support env var: HTTP_ PROXY, NO_ PROXY, and HTTPS_ PROXY. So changing it into feature ask.