Validate slot name when using scm credentials

Improvements

1. When deploying a project to a function app slot, perform app-name and slot-name validation against the SCM credentials.
2. Update azure-actions-appservice-rest to 1.0.8
3. Update azure-actions-webclient to 1.0.8

Fix build issues when using scm credentials

Fixes

1. Remove redundant oryx build on Linux Consumption function app deployment. Since the Linux Consumption /api/zipdeploy endpoint performs oryx build by default, this will introduce an overhead during the deployment. We manually disabled this oryx build action by setting ENABLE_ORYX_BUILD and SCM_DO_BUILD_DURING_DEPLOYMENT to false.
2. Fix an issue when detecting OS platform for function app. Using scm credentials for deployment will limit this GitHub Action access in Azure Resource Manager. Now we handle the failure gracefully and mark the OS platform as unknown.

Suppress informational warnings

Improvements

1. Suppress informational warnings when user using SCM credentials for function app deployment
2. Fix typo "crednetial" by replacing it with "credential"

Add support for publish-profile credentials

New Features

1. Azure Functions Github Action now accept publish-profile input, which helps developers who cannot create Azure Service Principal to deploy to function apps using publish profile credentials.

Improvements

1. Ensure the app settings propagate to Kudu container when changing WEBSTITE_RUN_FROM_PACKAGE to 1 for Windows function apps.
2. Back up app setting for deployments using publish-profile credentials. Restore the original app settings after the deployment is finished.

GitHub Action for Azure Functions

Automate your GitHub Actions workflow to deploy Azure Functions

Usage

Sample workflow to build and deploy a Node.js Function App to Azure

License

GitHub Action for Azure Function App is licensed under the MIT License.