[Bug Report]: Automation Account module failing on one of the test files due to the jobSchedule property

[ahmadabdalla]

Describe the bug

We have introduced a change a while back that replaces the name of the job schedule name from a GUID into the uniqueString()
function. As per the below commit history:

The unique string function does not produce a GUID according to the requirement of this parameter. Hence that is failing the job and we get the below error:

{
  "code": "DeploymentFailed",
  "message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.",
  "details": [
    {
      "code": "BadRequest",
      "message": ""
    }
  ]
}

The jobSchedule name has to be a GUID and is not something we can control. Running the template multiple times although submitting a new guid, doesn't actually keep adding more job schedules. It just links the runbook to the schedule and maintains the original guid created

To reproduce

Simply run the automation accounts module workflow

Code snippet

name: contains(jobSchedule, 'name') ? jobSchedule.name : uniqueString(name, subscription().id)



@description('Optional. Name of the Automation Account job schedule. Must be a GUID. If not provided, a new GUID is generated.')
param name string = uniqueString(automationAccountName, subscription().id)

Relevant log output

{
  "code": "DeploymentFailed",
  "message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.",
  "details": [
    {
      "code": "BadRequest",
      "message": ""
    }
  ]
}