Question

Your team ships a monolithic web app deployed with a single GitHub Actions workflow. The product owner wants to release a new checkout flow to only 10% of users first, then gradually increase exposure over several days, without triggering a new deployment for each increase. You already store application configuration in Azure App Configuration. What is the most appropriate way to implement this progressive exposure requirement?

Accepted Answer

Create an Azure App Configuration feature flag with a percentage (targeting) filter for the checkout flow, and adjust the rollout percentage in App Configuration as exposure increases.

Answer

Use a GitHub Actions matrix strategy to deploy separate builds to 10%, 25%, 50%, and 100% of the production servers on a schedule.

Answer

Configure an Azure Pipelines ring-based deployment that deploys the new binary to progressively larger production slots each day.

Answer

Add a manual approval check in the GitHub Actions production environment for each percentage increase so a reviewer redeploys the app.