Describe the issue:
An error occurred while running azd provision according to the "adding a custom domain name" section of README.md. The error is shown as following:

Repro Steps:

1. Run npm i
2. Run npm run env:init
3. Run azd auth login
4. Add SERVICE_WEB_CUSTOM_DOMAIN_NAME=www.xshtest.com in .env.local file
5. Run azd provision

Expected behavior:
Run command azd provision successfully.

@CMeeg and @hemarina for notification.

Description of issue / Reproduction steps

• Next.js provides an option to enable compression of resources using gzip
• After enabling this option and deploying to Azure any request for resources that our routed through the CDN result in a request timeout
• To cut a long story short the issue is caused by Range requests issued from the CDN to the origin, and is described on the accepted answer to an issue raised here along with some potential solutions/workarounds:
  1. Disable caching in the CDN profile (this will cause CDN to not send range requests to the origin)
  2. Change the origin to ignore range requests (treating them as regular non-range requests and returning 200s instead of 206s)
  3. Disable compression at the origin
• Disabling range requests from the CDN to the Origin doesn't look to be an option (or at least would be an uphill battle I'm sure) unfortunately as this behaviour is "baked in" to how the CDN functions

Expected behaviour

• Requests for resources routed through the CDN to the origin receive an appropriate response in an appropriate timeframe

Actual behaviour

• Requests for resources routed through the CDN to the origin consistently timeout and fail to respond

Description of issue / Reproduction steps

• When running azd provision for the first time the image mcr.microsoft.com/azuredocs/containerapps-helloworld:latest is deployed to the main Container app
• When running azd deploy the web service is built into an image and deployed to to main container app
• If you run azd provision again after azd deploy the mcr.microsoft.com/azuredocs/containerapps-helloworld:latest is deployed to the main Container app again

Expected behaviour

• When running azd provision after azd deploy the image deployed to the main Container app doesn't change

Actual behaviour

• When running azd provision after azd deploy the image deployed to the main Container app changes to mcr.microsoft.com/azuredocs/containerapps-helloworld:latest

Description of issue / Reproduction steps

• The fix for #5 worked when running locally, but not when running in a pipeline
• When running in a pipeline the SERVICE_WEB_IMAGE_NAME env var is not available so cannot be provided to the bicep deployment

Expected behaviour

• When running in a pipeline azd provision should not change the image deployed to the main Container app

Actual behaviour

• When running in a pipeline azd provision changes the image deployed to the main Container app to mcr.microsoft.com/azuredocs/containerapps-helloworld:latest

Describe the issue:
When perform step 2 of Create an Environment, if push local code directly to the repository, there is no Environments in Settings under the repository. It is recommended to updat step 2 to "Go to the forked repository in GitHub".

Expected behavior:
Able to create the environment normally.

@CMeeg and @hemarina for notification.

Describe the issue:
The assigned role Contributor does not match the required role Role Based Access Control Administrator in GitHub Actions and Azure DevOps Pipelines in README.md, we should add Role Based Access Control Administrator, not Contributor role. the error is as follows:

Suggestion:
Change Contributor to Role Based Access Control Administrator (Preview)

@CMeeg and @hemarina for notification.

Describe the issue:
Follow the steps of README.md to select custom domain name, and find that this operation is disabled in Container Apps Environment, as follows:

Expected behavior:
Adding a custom domain name successful.

@CMeeg and @hemarina for notification.