CaseSensitiveDeploymentParameterNamesFound

[sangling]

The deployment parameters are using case sensitive names. The error parameter name(s): parAllowHubVpnGatewayTransit,parSpokeToHubRouteTableName

Overview/Summary

Fixed parameter cases in Orchestration - hubPeeredSpoke which was causing CaseSensitiveDeploymentParameterNamesFound error

This PR fixes/adds/changes/removes

1. Corrected case of parSpokeToHubRouteTableName in hubPeeredSpoke.parameters.all.json
2. Corrected case of parAllowHubVpnGatewayTransit in hubPeeredSpoke.parameters.all.json
3. Corrected case of parSpokeToHubRouteTableName in hubPeeredSpoke.vwan.parameters.all.json
4. Corrected case of parAllowHubVpnGatewayTransit in hubPeeredSpoke.vwan.parameters.all.json

Breaking Changes

1. CaseSensitiveDeploymentParameterNamesFound - The deployment parameters are using case sensitive names. The error parameter name(s): parSpokeToHubRouteTableName,parAllowHubVpnGatewayTransit

Testing Evidence

Error:

Tested:

As part of this Pull Request I have

• Read the Contribution Guide and ensured this PR is compliant with the guide
• Ensured the resource API versions in .bicep file/s I am adding/editing are using the latest API version possible
• Checked for duplicate Pull Requests
• Associated it with relevant GitHub Issues
• (ALZ Bicep Core Team Only) Associated it with relevant ADO Items
• Ensured my code/branch is up-to-date with the latest changes in the main branch
• Performed testing and provided evidence.
• Updated one or more of the following tests (if required)
  • Unit
  • Linting
  • E2E (End-To-End)
  • ValidateAzCloud (Base validation in Azure Cloud)
  • ValidateMcCloud (Base validation in Azure China Cloud)
• Updated relevant and associated documentation (e.g. Contribution Guide, Module READMEs, Wiki Docs etc.)
• If relevant, created or updated Code Tours here

[sangling]

@microsoft-github-policy-service agree

[jtracey93]

Thanks for this @sangling LGTM. Will test and merge if all okay

[jtracey93]

/azp run validateazcloud

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).