Blueprint module does not accept ResourceGroup.Name values with long computed expressions

Describe the bug Receiving a validation error through the Az.BluePrint powershell module regarding the importing of a Blueprint with a computed ResourceGroup.name value. The error indicates only 90 characters are supported in the resource group name. However, this is not actually true as the value allows [] expansion values exceeding 90 characters.

Expected behavior The computable value should be accepted.

Actual behavior (include Exception or Stack Trace) Import-AzBlueprintWithArtifact : 'Name' exceeds maximum length of '90'.

To Reproduce

    "resourceGroups": {
            "ApplicationResourceGroup": {
                "location": "[parameters('l')]",
                "name": "[concat(parameters('u'),'-',parameters('e'),'-',parameters('d'),'-',parameters('a'),'-rg')]"
            }
        }

Attempt to import the Blueprint, and receive the error.

[ScottMetzel]

Thanks for the information @alex-frankel; I caught that announcement and look forward to template specs!

As a workaround, I simply shortened some parameter names to get the string value of the function at or below 90 characters in length… works fine otherwise.

[alex-frankel]

This is an issue with our APIs, not with the SDK. With the planned changes to move blueprint definitions to template specs, this is not likely something we are going to fix. We just announced templateSpecs at build, so details are a bit scarce, but we should have more info to share in 1-2 months.