| master | dev | |
|---|---|---|
| Coverage |  |
 |
| Unit Test |  |
 |
| .NETCore Windows |  |
 |
| .NETCore Linux |  |
 |
| Java Windows |  |
 |
| Java Linux |  |
 |
| Node JS Windows |  |
 |
| Node JS Linux |  |
 |
| PowerShell Windows |  |
 |
| Python Linux |  |
 |
With the Azure Functions GitHub Action, you can automate your workflow to deploy Azure Functions.
Get started today with a free Azure account!
The repository contains a GitHub Action to deploy your function app project into Azure Functions. If you are looking for a GitHub Action to deploy your customized container image into an Azure Functions container, please consider using functions-container-action.
The definition of this GitHub Action is in action.yml.
Kudu zip deploy method is used by the action for deployment of Functions.
If you have extension project(s) in your repo, these templates will NOT resolve the extensions.csproj in your project. If you want to use binding extensions (e.g. Blob/Queue/EventHub Triggers), please consider registering Azure Functions binding extensions in your host.json.
Alternatively, you can add a - run: dotnet build --output ./bin step before functions-action step.
"Remove additional files at destination" is not supported by Kudu deploy method used in this action and should be handled separately. When a new build is deployed with zipdeploy, files and directories that were created by the previous deployment but are no longer present in the build will be deleted. Any other files and directories found in the site that aren't being overwritten by the deployment, such as those placed there via FTP or created by your app during runtime, will be preserved.
Using publish profile as deployment credential is recommended if you are not the owner of your Azure subscription. Follow these steps to configure your workflow to use the publish profile from your function app.
- In Azure portal, go to your function app.
- Click Get publish profile and download .PublishSettings file.
- Open the .PublishSettings file and copy the content.
- Paste the XML content to your GitHub Repository > Settings > Secrets > Add a new secret > AZURE_FUNCTIONAPP_PUBLISH_PROFILE
- Use one of the above workflow templates as a reference to build your workflow in
.github/workflows/directory. - Change variable values in
env:section according to your function app. - Commit and push your project to GitHub repository, you should see a new GitHub workflow initiated in Actions tab.
Note:
If you want to deploy to Linux Consumption plan and your app contains executable file(custom handler, chrome in Puppeteer/Playwright etc), you need to use this way in order to keep executable permission.
Follow these steps to configure your workflow to use an Azure Service Principal for RBAC and add them as a GitHub Secret in your repository.
- Download Azure CLI from here, run
az loginto login with your Azure credentials. - Run Azure CLI command
az ad sp create-for-rbac --name "myApp" --role contributor \
--scopes /subscriptions/{subscription-id}/resourceGroups/{resource-group}/providers/Microsoft.Web/sites/{app-name} \
--sdk-auth
# Replace {subscription-id}, {resource-group}, and {app-name} with the names of your subscription, resource group, and Azure function app.
# The command should output a JSON object similar to this:
{
"clientId": "<GUID>",
"clientSecret": "<GUID>",
"subscriptionId": "<GUID>",
"tenantId": "<GUID>",
(...)
}
- Copy and paste the json response from above Azure CLI to your GitHub Repository > Settings > Secrets > Add a new secret > AZURE_RBAC_CREDENTIALS
- Use Windows DotNet Function App RBAC template as a reference to build your workflow in
.github/workflows/directory. - Change variable values in
env:section according to your function app. - Commit and push your project to GitHub repository, you should see a new GitHub workflow initiated in Actions tab.
Azure Functions GitHub Action is supported for the Azure public cloud as well as Azure government clouds ('AzureUSGovernment' or 'AzureChinaCloud') and Azure Stack ('AzureStack') Hub. Before running this action, login to the respective Azure Cloud using Azure Login by setting appropriate value for the environment parameter.
- app-name: The function app name on Azure. (e.g. if your function app can be accessed via https://your-site-name.azurewebsites.net/, then app-name should be
your-site-name). - package: This is the location in your project to be published. By default, this value is set to
., which means all files and folders in the GitHub repository will be deployed. - slot-name: This is the slot name to be deployed to. By default, this value is empty, which means the GitHub Action will deploy to your main production site. When this setting points to a non-production slot, please ensure the publish-profile parameter contains the credentials from the function app slot instead of the main production site.
- publish-profile: This is the credentials that will be used during the deployment. It should contain a piece of XML content from your .PublishSettings file. You can acquire .PublishSettings by visiting the Azure Portal -> Your Function App -> Overview -> Get Publish Profile. We highly recommend setting the content in GitHub secrets since it contains sensitive information such as your site URL, username, and password. When the publish profile is rotated in your function app, you also need to update the GitHub secrets. Otherwise will result in a 401 error when accessing the /api/settings endpoint.
- respect-pom-xml: Allow GitHub Action to derive Java function app's artifact from pom.xml for deployments. By default, it is set to
false, which means in the package parameter needs to point to your Java function app's artifact (e.g. ./target/azure-functions/). It is recommended to set package to.and respect-pom-xml totruewhen deploying Java function apps. - respect-funcignore: Allow GitHub Action to parse your .funcignore file and exclude files and folders defined in it. By default, this value is set to
false. If your GitHub repo contains .funcignore file and want to exclude certain paths (e.g. text editor configs .vscode/, Python virtual environment .venv/), we recommend setting this totrue. - scm-do-build-during-deployment: Allow Kudu site (e.g. https://your-site-name.scm.azurewebsites.net/) to perform pre-deployment operation. By default, this is set to
false. If you don't want to resolve the dependencies in the GitHub Workflow, and instead, you want to control the deployments in Kudu / KuduLite, you may want to change this setting totrue. For more information on SCM_DO_BUILD_DURING_DEPLOYMENT setting, please visit our Kudu doc. - enable-oryx-build: Allow Kudu site to resolve your project dependencies with Oryx. By default, this is set to
false. If you want to use Oryx to resolve your dependencies (e.g. remote build) instead of GitHub Workflow, please consider setting scm-do-build-during-deployment and enable-oryx-build totrue.
- Checkout Checkout your Git repository content into GitHub Actions agent.
- Azure Login Login with your Azure credentials for function app deployment authentication.
- Environment setup actions
- Setup DotNet Build your DotNet core function app or function app extensions.
- Setup Node Resolve Node function app dependencies using npm.
- Setup Python Resolve Python function app dependencies using pip.
- Setup Java Resolve Java function app dependencies using maven.
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.
When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.