This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I am migrating quite some projects from local servers to Azure functions. In these projects we use our own created Python modules which we are hosting on private GitHub repo. When developing locally or on a Ubuntu server, we can add the ssh-key to the GitHub repo and we can do:
pip install git+ssh://******@github.com/org-name/package-name.git
This way we install our private modules.
But how would we do this on an Azure functions where we have git+ssh://******@github.com/org-name/package-name.git in our requirements.txt together with other open source packages like requests==2.24.0. I am not sure how to add ssh to our function app.
Or is there a better solution for this?
I believe there is no provision to setup an ssh-key for remote builds.
The alternate would be to either use local build or setup CI/CD Pipeline in Azure Devops or Github Actions to perform the build and deploy to Azure Functions.
That actually makes sense, will try it with GitHub Actions, thanks.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(252.8, 39%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAB%3C/text%3E%3C/svg%3E)
Did this solution work for you? We are running into a similar issue. @Pramod Valavala how do we use github actions which has requirements.txt with dependency on a private repo ( git+ssh)? We are using Azure/functions-action but somehow we get error with pip-install on Oryx build step.
@Abhijit Badve You would have to install the required SSH private keys using an action like webfactory/ssh-agent when working with private repositories.
Just to be clear, we are using ssh-agent in our github actions. To make sure ssh keys are valid/working, we use pip install in one of the earlier steps, and it runs without issue. After digging in this more, we found that when we use az login with SP for authentication, the deployment step fails in pip-install. We switched to using publish profile and it is working for us. Just want to note here that as of azure-functions@v1 version with azure login method does not work if we have links to private repositories in the requirements.txt.