Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ARM] Invalid JSON format for az deployment group create #28965

Open
TsuyoshiUshio opened this issue May 15, 2024 · 2 comments
Open

[ARM] Invalid JSON format for az deployment group create #28965

TsuyoshiUshio opened this issue May 15, 2024 · 2 comments
Labels
Auto-Assign Auto assign by bot Auto-Resolve Auto resolve by bot Azure Deployments az deployment/bicep/stack/deployment-scripts/ts/group export bug This issue requires a change to an existing behavior in the product in order to be resolved. Service Attention This issue is responsible by Azure service team.

Comments

@TsuyoshiUshio
Copy link
Contributor

Describe the bug

I deploy bicep templates by following command.

az deployment group create --resource-group $resourceGroupName -o json --template-file ..\BicepTemplates\resources.bicep --parameters

However, I received Invalid JSON format. For sharing part of it. That prevent the Json Parsing.

image

Related command

az deployment group create --resource-group $resourceGroupName -o json --template-file ..\BicepTemplates\resources.bicep --parameters

Errors

Not the error message. The result object the following returns invalid JSON.

    $result = az deployment group create --resource-group $resourceGroupName -o json --template-file ..\BicepTemplates\resources.bicep --parameters `
        app_name="$appName" `
        location="$location" `
        function_plan_os="$functionPlanOS" `
        runtime_version="`"$runtimeVersion`"" `
        sku="$sku" `
        network="$network"

Issue script & Debug output

I'm MSFT guy, reach out to me, then I'll give whole information. tsushi.

Expected behavior

I expect the result should be able to parse as Json.

Environment Summary

az --version
azure-cli 2.59.0 *

core 2.59.0 *
telemetry 1.1.0

Extensions:
application-insights 0.1.14
azure-devops 0.26.0

Dependencies:
msal 1.27.0
azure-mgmt-resource 23.1.0b2

Python location 'C:\Program Files\Microsoft SDKs\Azure\CLI2\python.exe'
Extensions directory 'C:\Users\tsushi.azure\cliextensions'

Python (Windows) 3.11.8 (tags/v3.11.8:db85d51, Feb 6 2024, 22:03:32) [MSC v.1937 64 bit (AMD64)]

Legal docs and information: aka.ms/AzureCliLegal

Additional context

No response

@TsuyoshiUshio TsuyoshiUshio added the bug This issue requires a change to an existing behavior in the product in order to be resolved. label May 15, 2024
Copy link

Hi @TsuyoshiUshio,

2.59.0 is not the latest Azure CLI(2.60.0).

If you haven't already attempted to do so, please upgrade to the latest Azure CLI version by following https://learn.microsoft.com/en-us/cli/azure/update-azure-cli.

@azure-client-tools-bot-prd azure-client-tools-bot-prd bot added the Auto-Resolve Auto resolve by bot label May 15, 2024
@yonzhan
Copy link
Collaborator

yonzhan commented May 15, 2024

Thank you for opening this issue, we will look into it.

@microsoft-github-policy-service microsoft-github-policy-service bot added Auto-Assign Auto assign by bot Azure Deployments az deployment/bicep/stack/deployment-scripts/ts/group export Service Attention This issue is responsible by Azure service team. labels May 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Auto-Assign Auto assign by bot Auto-Resolve Auto resolve by bot Azure Deployments az deployment/bicep/stack/deployment-scripts/ts/group export bug This issue requires a change to an existing behavior in the product in order to be resolved. Service Attention This issue is responsible by Azure service team.
Projects
None yet
Development

No branches or pull requests

2 participants