`wordpress_azure_ci_cd.md`: Source Integration (CI/CD) via Deployment Center not available for apps provisioned with `sitecontainers` model

Open Beginner friendly
#220 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Quiet
Tech stack
azure, github-actions

Research direction

Start by reading WordPress/wordpress_azure_ci_cd.md and verify the documented Deployment Center flow against the issue's linuxFxVersion command and linked Microsoft guidance. Done means the page explains the sitecontainers limitation, how to identify the provisioning model, and the manual GitHub Actions workaround.

Written by the indexing model from the issue text.

Description

Description

Summary

The CI/CD documentation at WordPress/wordpress_azure_ci_cd.md states that GitHub source integration is available for WordPress images using PHP 8.2 or greater. However, it does not mention a critical limitation: apps provisioned using the newer SiteContainers model (linuxFxVersion = "sitecontainers") do not have the Source Integration UI available in the Azure Portal Deployment Center.

Observed Behavior

When a WordPress app is provisioned from Azure Marketplace and the resulting app has:

"linuxFxVersion": "sitecontainers",

The Deployment Center blade shows only the Containers / Logs / FTPS Credentials tabs. The Source tab (GitHub / Azure Repos integration) is absent entirely.
This affects apps provisioned more recently via the Marketplace WordPress offering, regardless of the PHP version or container image tag used (e.g., mcr.microsoft.com/appsvc/wordpress-debian-php:8.4).

Expected Behavior

The documentation should:

  1. Clarify that the portal-based source integration setup described in wordpress_azure_ci_cd.md is only applicable to apps where linuxFxVersion is not sitecontainers (e.g., WORDPRESS|8.x).
  2. Document the workaround for sitecontainers-based apps: CI/CD via GitHub Actions is still possible by manually setting up a workflow, as described in Manually set up a GitHub Actions workflow.
  3. Explain how to identify which provisioning model an app is using (e.g., check linuxFxVersion via Azure CLI or Portal → JSON View).
Steps to Reproduce
  1. Create a new WordPress app via Azure Marketplace.
  2. Navigate to Deployment Center in the Azure Portal.
  3. Observe that only Containers / Logs / FTPS Credentials tabs are shown — no Source tab.
  4. Confirm linuxFxVersion = sitecontainers via:
    az webapp config show --name <app> --resource-group <rg> --query linuxFxVersion
    
Suggested Documentation Addition

Add a note such as:

Note: If your app was provisioned using the SiteContainers model (linuxFxVersion = "sitecontainers"), the source integration option will not appear in Deployment Center. In this case, you can still set up GitHub Actions CI/CD manually. See Manually set up a GitHub Actions workflow.

Dominant language
HCL
Stars
139
Forks
84
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/wordpress-linux-appservice

All issues in Azure/wordpress-linux-appservice

Similar issues

More Cloud issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.