-
Notifications
You must be signed in to change notification settings - Fork 74
Overview
The Azure Functions GitHub Action (a.k.a. Azure/functions-action) is used by customers who has their code in GitHub source control system. A GitHub Workflow consists of multiple GitHub Actions to achieve automation propose in Continuous Integration / Continuous Deployment scenario.
To use Azure/functions-action, customers need to have an existing function app GitHub repository, or upload their function app code onto a new one.
There are two ways for our customer to use our action:
- Follow the template in https://github.com/Azure/functions-action#workflow-templates to create a .github/workflows/.yml file which will be the template for GitHub Hosted Runners to start the execution.
- In Azure Portal, use Deployment Center and choose the GitHub as their source to setup the pipeline. In this case, a new .github/workflows/.yml file will be generated in their GitHub repository.
In conclusion, anything that the GitHub Hosted Runners will consume is the .yml file.
The functions action is only responsible for packaging everything from the GitHub Hosted Runners to Azure Functions on the cloud. There're a set of parameters which can be used https://github.com/Azure/functions-action#github-action-parameters. The metadata of the action are defined in action.yml file. This includes the entrypoint, how it looks in the marketplace, and what are the acceptable parameters.
Here's the list of release versions. The title of each releases does not matter, but the version tag needs to be carefully updated. Customers will use Azure/functions-action@<version> to fetch specific version onto their GitHub Runners.