You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add prod GitHub Actions for Function App and SWA deploy
Added workflows for production deployment:
- func-deploy-prod.yml: Builds and deploys .NET Azure Function App using OIDC and managed identity on main branch changes.
- swa-deploy-prod.yml: Builds and deploys .NET Static Web App, including config copy, using deployment token on main branch changes.
name: Function App - PROD - Build and Deploy (OIDC)
2
+
3
+
# CONFIGURATION
4
+
#
5
+
# This workflow can be used to deploy your .NET project to a function app on any hosting plan, except for Container Apps (which uses functions-container-action).
6
+
#
7
+
# For an overview of using GitHub workflows with Azure Functions, see https://learn.microsoft.com/azure/azure-functions/functions-how-to-github-actions
8
+
#
9
+
# 1. Configure a federated identity credential to your GitHub branch on an Azure user-assigned managed identity.
10
+
# For instructions, follow the README at https://github.com/Azure/functions-action#use-oidc-recommended
11
+
#
12
+
# 2. Add the following values from the managed identity to your repo's variables:
13
+
# AZURE_CLIENT_ID
14
+
# AZURE_TENANT_ID
15
+
# AZURE_SUBSCRIPTION_ID
16
+
# For instructions on creating repo variables, see https://docs.github.com/actions/writing-workflows/choosing-what-your-workflow-does/store-information-in-variables#defining-configuration-variables-for-multiple-workflows
17
+
#
18
+
# 3. Ensure your workflow is triggered by your desired event. By default, it is triggered when a push is made to main, and it can be manually run.
19
+
# For guidance on event triggers, see https://docs.github.com/actions/writing-workflows/choosing-when-your-workflow-runs/triggering-a-workflow#using-events-to-trigger-workflows
0 commit comments