Azure App Service GitHub Workflow Generates Oryx Build Instead of ZIP Deploy

Question

Issue Description:

I am provisioning an Azure App Service with GitHub CI/CD integration via Terraform. During the resource provisioning, the GitHub Actions workflow is automatically generated. However, the generated workflow includes the Oryx build step (azure/appservice-build@v2).

In contrast, when I create the Azure App Service manually through the Azure portal with the same GitHub integration, the generated workflow does not include the Oryx build step. Instead, it uses a different approach where it:

Creates and activates a Python virtual environment

Installs dependencies

Packages the app as a ZIP artifact

Deploys the ZIP package without invoking Oryx build

I want the Terraform-generated workflow to match the Azure portal-generated workflow, specifically to avoid the Oryx build step and instead use the ZIP deployment approach.

What I want:

Terraform-created Azure App Service with GitHub Actions workflow generated without the appservice-build@v2 (Oryx build) step.

The workflow should instead create a Python virtual environment, install dependencies, zip the app, and deploy the ZIP package (like the portal-generated workflow).

Additional details:

I have tried configuring app settings like WEBSITE_RUN_FROM_PACKAGE=1 and SCM_DO_BUILD_DURING_DEPLOYMENT=false but the Terraform-generated workflow still includes Oryx build.

I would like to know if there is any Azure App Service Terraform parameter or configuration that influences the generated workflow type, or if there's a recommended approach to get the ZIP deployment workflow generated automatically.

Answer 1

Hi @Naveen prabhu
If you want your GitHub Actions workflow for Azure App Service to skip the Oryx build step and use ZIP deployment instead, you'll need to manually update the workflow that Terraform creates. Currently, the Terraform provider for Azure App Service doesn't offer a direct way to change the workflow type or remove the Oryx build step.

After the workflow is generated, you can edit the .github/workflows/main.yml file in your repository. Add steps for setting up a Python virtual environment, installing dependencies, zipping your app, and deploying the ZIP file.

Also, make sure your app settings are correct. Since setting WEBSITE_RUN_FROM_PACKAGE=1 and SCM_DO_BUILD_DURING_DEPLOYMENT=false hasn't worked, manually updating the workflow file remains the most effective solution.

References:

• Configure continuous deployment to Azure App Service
• Deploy to Azure infrastructure with GitHub Actions
  Let me know if you have any further assistances needed.