能否通过GitHub Actions部署至唯一动态Azure Function App部署槽并返回URL

完全可以实现你的需求，通过GitHub Actions为每个PR动态创建Azure Function App部署槽并关联Static Web Apps预览环境，具体步骤如下：

1. 前置准备 #

• 确保你的Azure Function App已启用部署槽功能（Azure门户中Function App → 部署 → 部署槽，开启后支持多槽部署）
• 在GitHub仓库中配置Azure凭据密钥：AZURE_CREDENTIALS（用于Azure CLI登录）、AZURE_FUNCTIONAPP_PUBLISH_PROFILE（用于Function部署）、AZURE_STATIC_WEB_APPS_API_TOKEN（用于Static Web Apps部署）

2. GitHub Actions工作流设计 #

创建一个针对PR触发的工作流，完成「动态创建部署槽 → 部署Function到槽 → 获取槽URL → 部署Static Web Apps预览环境并注入API地址」的全流程：

name: PR Staging Environment Deployment
on:
  pull_request:
    types: [opened, synchronize, reopened]
  pull_request_closed:
    types: [closed]

jobs:
  deploy-staging:
    if: github.event.action != 'closed'
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      # 登录Azure账号
      - name: Azure Login
        uses: azure/login@v2
        with:
          creds: ${{ secrets.AZURE_CREDENTIALS }}

      # 生成唯一部署槽名（基于PR编号）
      - name: Generate Unique Slot Name
        id: slot-generator
        run: echo "slot-name=pr-${{ github.event.number }}" >> $GITHUB_OUTPUT

      # 创建部署槽（若不存在则创建，继承生产环境配置）
      - name: Create Function Deployment Slot
        run: |
          az functionapp deployment slot create \
            --name YOUR_FUNCTION_APP_NAME \
            --resource-group YOUR_RESOURCE_GROUP_NAME \
            --slot ${{ steps.slot-generator.outputs.slot-name }} \
            --configuration-source YOUR_FUNCTION_APP_NAME \
            --output none

      # 部署Function代码到目标槽
      - name: Deploy Function App to Slot
        uses: azure/functions-action@v1
        with:
          app-name: YOUR_FUNCTION_APP_NAME
          slot-name: ${{ steps.slot-generator.outputs.slot-name }}
          package: ./path/to/function/code
          publish-profile: ${{ secrets.AZURE_FUNCTIONAPP_PUBLISH_PROFILE }}

      # 获取部署槽的访问URL
      - name: Retrieve Slot URL
        id: slot-url
        run: |
          host_name=$(az functionapp show \
            --name YOUR_FUNCTION_APP_NAME \
            --resource-group YOUR_RESOURCE_GROUP_NAME \
            --slot ${{ steps.slot-generator.outputs.slot-name }} \
            --query defaultHostName -o tsv)
          echo "url=https://$host_name" >> $GITHUB_OUTPUT

      # 部署Static Web Apps预览环境，注入API地址环境变量
      - name: Deploy Static Web Apps PR Preview
        uses: Azure/static-web-apps-deploy@v1
        with:
          azure_static_web_apps_api_token: ${{ secrets.AZURE_STATIC_WEB_APPS_API_TOKEN }}
          repo_token: ${{ secrets.GITHUB_TOKEN }}
          action: "upload"
          app_location: "./path/to/frontend/code"
          api_location: "" # 独立API无需填写此项
          output_location: "./dist" # 前端构建产物目录
          environment_variables: |
            API_URL=${{ steps.slot-url.outputs.url }}

  # PR关闭时清理对应的部署槽，避免资源浪费
  cleanup-slot:
    if: github.event.action == 'closed'
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - name: Azure Login
        uses: azure/login@v2
        with:
          creds: ${{ secrets.AZURE_CREDENTIALS }}

      - name: Generate Slot Name
        id: slot-generator
        run: echo "slot-name=pr-${{ github.event.number }}" >> $GITHUB_OUTPUT

      - name: Delete Deployment Slot
        run: |
          az functionapp deployment slot delete \
            --name YOUR_FUNCTION_APP_NAME \
            --resource-group YOUR_RESOURCE_GROUP_NAME \
            --slot ${{ steps.slot-generator.outputs.slot-name }} \
            --yes \
            --output none

3. 关键注意事项 #

• 环境变量注入：前端代码需通过读取API_URL环境变量来调用对应槽的API接口，确保请求指向当前PR的staging环境
• 资源清理：工作流中包含PR关闭时删除槽的逻辑，避免闲置槽产生不必要的费用
• 权限控制：确保Azure凭据拥有Microsoft.Web/sites/slots/write权限，以创建/删除部署槽
• 配置继承：创建槽时通过--configuration-source参数继承生产环境的应用设置、连接字符串等，减少重复配置

内容的提问来源于stack exchange，提问作者Skenflow