Azure AppSettings to be made available during build

[JasonKleban]

Feature Request

Oryx does a build on the target Static Web App of a vite application, say, but cannot incorporate Azure-configured App Settings during the build.

resource "azurerm_static_web_app" "home" {
  ...

  app_settings = {
    ...
    "VITE_OTHER_DOMAIN" = local.domain_other
  }
}

Something like the above will not be available to Vite during the build as process.env.VITE_OTHER_DOMAIN or import.meta.env.VITE_OTHER_DOMAIN which is the only time we'd have a chance to inject such values in a static web app.

Please add support for something like the following, or please explain how this is already supported?

    - name: Deploy App
      uses: Azure/static-web-apps-deploy@v1
      with:
        azure_static_web_apps_api_token: ...
        action: "upload"
        api_location: "apps/api"
        app_location: "apps/site"
        output_location: "dist"
        include_app_settings_during_build: [ "VITE_OTHER_DOMAIN", ... ]

[JasonKleban]

Also not having any luck with the following technique - I don't see any evidence that the PRE_BUILD_COMMAND is being run. Though clunky, this would be good enough for me if it worked:

resource "azurerm_static_web_app" "home" {
  ...

  app_settings = {
    ...
    "PRE_BUILD_COMMAND" = "export VITE_OTHER_DOMAIN=\"${local.domain_other}\"; printenv; echo \"!!!!!!\""
  }
}

This seems to work, but requires making the vars available in the github action which is much sloppier (either a much more complicated integration from github actions to get secrets from Azure OR a likely duplication of this setting with Azure which needs to be kept in sync 🤮 )

    - name: Deploy App
      uses: Azure/static-web-apps-deploy@v1
      with:
        azure_static_web_apps_api_token: ...
        action: "upload"
        api_location: "apps/api"
        app_location: "apps/site"
        output_location: "dist"
      env:
        VITE_OTHER_DOMAIN: "[Some value Known Directly By Github Actions environment]"