(blocker) error executing provision (BCP332)

[nitya]

Describe the bug

The azd up command fails with a provisioning error:

ERROR: error executing step command 'provision': initializing provisioning manager: failed to compile bicepparam template: failed running bicep build: exit code: 1, stdout: , stderr: /workspaces/document-generation-solution-accelerator/infra/deploy_app_service.bicep(124,5) : Warning BCP037: The property "name" is not allowed on objects of type "AppServicePlanProperties". Permissible properties include "freeOfferExpirationTime", "hostingEnvironmentProfile", "hyperV", "isSpot", "isXenon", "maximumElasticWorkerCount", "perSiteScaling", "spotExpirationTime", "targetWorkerCount", "targetWorkerSizeId", "workerTierName". If this is a resource type definition inaccuracy, report it using https://aka.ms/bicep-type-issues. [https://aka.ms/bicep/core-diagnostics#BCP037]
/workspaces/document-generation-solution-accelerator/infra/main.bicepparam(3,25) : Error BCP332: The provided value (whose length will always be greater than or equal to 20) is too long to assign to a target for which the maximum allowable length is 10. [https://aka.ms/bicep/core-diagnostics#BCP332]

This prevents me continuing further with testing.

To Reproduce
Steps to reproduce the behavior:

1. Launched GitHub Codespaces
2. Manually checked that I had required quota in region (eastus worked)
3. Ran azd auth login - successful
4. Ran azd up - failed with error above

Expected behavior

Expected azd up to complete and provision the required resource group. I manually verified that the resource group was never created.

[Vinay-Microsoft]

Hi @nitya quick question, do you remember what was the env. name you used for this deployment?

[nitya]

@Vinay-Microsoft not exactly but it was likely something like "nitya-docgenazd-test".

[Roopan-Microsoft]

Hi @nitya - Thanks for your feedback.

The maximum supported length for the environment name is 20. Your provided name and length were valid. However, we encountered a conflict in the code, which has now been resolved. #323

Please re-deploy and let us know if any issue, happy to help!