az lab environment create no longer accepts JSON-escaped parameters on --parameters #30206
Labels
Auto-Assign
Auto assign by bot
bug
This issue requires a change to an existing behavior in the product in order to be resolved.
customer-reported
Issues that are reported by GitHub users external to the Azure organization.
Devtestlab
az lab
Service Attention
This issue is responsible by Azure service team.
Describe the bug
For years I've been using
az lab environment create
to create DTL environments, using JSON-escaped parameters on --parameters to pass the template parameters, but this no longer works with the version 2.65.0 (not sure when it appeared).Could it be a regression introduced by #29878 ?
Related command
az lab environment create
Errors
InvalidArgumentValue: --parameters: File '[ { "name": "provisionSharePoint2016", "value": "false" }, { "name": "provisionSharePoint2019", "value": "false" }, { "name": "provisionSharePointSubscription", "value": "Subscription-Latest" }, { "name": "configureADFS", "value": "true" }, { "name": "enableHybridBenefitServerLicenses", "value": "true" }, { "name": "enableAutomaticUpdates", "value": "false" }, { "name": "adminUserName", "value": "yvand" }, { "name": "adminPassword", "value": "PASSWORD" }, { "name": "serviceAccountsPassword", "value": "PASSWORD" }, { "name": "addPublicIPAddress", "value": "SharePointVMsOnly" }, { "name": "RDPTrafficAllowed", "value": "10.20.30.40" }, { "name": "addAzureBastion", "value": "false" } ]' doesn't exist
Issue script & Debug output
Script:
Output:
Expected behavior
Triggers the creation of the DTL lab, using the JSON-escaped parameters passed to --parameters
Environment Summary
azure-cli 2.65.0
core 2.65.0
telemetry 1.1.0
Dependencies:
msal 1.31.0
azure-mgmt-resource 23.1.1
Python location '/opt/az/bin/python3'
Extensions directory '/home/yvand/.azure/cliextensions'
Python (Linux) 3.11.8 (main, Sep 25 2024, 11:33:44) [GCC 11.4.0]
Legal docs and information: aka.ms/AzureCliLegal
Your CLI is up-to-date.
Additional context
No response
The text was updated successfully, but these errors were encountered: