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

az monitor app-insights workbook create | Can't create workbook with serialized-data, too long for CLI #8422

Open
chkinney opened this issue Jan 17, 2025 · 1 comment
Assignees
Labels
Auto-Assign Auto assign by bot Azure CLI Team The command of the issue is owned by Azure CLI team customer-reported Issues that are reported by GitHub users external to the Azure organization. Monitor question The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Milestone

Comments

@chkinney
Copy link

Describe the bug

We are unable to create a pre-populated workbook using the Azure CLI due to the serialized data for the workbook being too long for the CLI tool.

The command returns an error status and the following output:

The command line is too long.

This error might originate from the shell itself. This command is being executed from Windows 11.

The input we are passing in, minified, is more than 28000 characters long and is a fairly large workbook. It is being passed in via the --serialized-data CLI parameter.

Related command

az monitor app-insights workbook create \
  --resource-name $uuid \
  --resource-group $rg \
  --kind shared \
  --category workbook \
  --display-name test \
  --source-id '/subscriptions/.../resourceGroups/.../providers/Microsoft.Insights/components/...' \
  --serialized-data $data

Errors

The command line is too long.

Issue script & Debug output

The command line is too long.

There is no other output. It's possible this error originates from the shell itself.

Expected behavior

I think passing in this much data via the CLI is expected to result in an error. Instead, I would expect to be able to pass in the serialized data through some other means, such as via stdin or a file.

Environment Summary

azure-cli 2.68.0

core 2.68.0
telemetry 1.1.0

Extensions:
application-insights 1.2.2
bastion 1.1.0

Dependencies:
msal 1.31.1
azure-mgmt-resource 23.1.1

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

Python (Windows) 3.12.8 (tags/v3.12.8:2dc476b, Dec 3 2024, 19:30:04) [MSC v.1942 64 bit (AMD64)]

Legal docs and information: aka.ms/AzureCliLegal

Your CLI is up-to-date.

Additional context

Adding a --serialized-data-file argument or accepting a special value to pipe in the serialized data via stdin would likely resolve this issue.

@chkinney chkinney added the bug This issue requires a change to an existing behavior in the product in order to be resolved. label Jan 17, 2025
@yonzhan
Copy link
Collaborator

yonzhan commented Jan 17, 2025

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

@microsoft-github-policy-service microsoft-github-policy-service bot added question The issue doesn't require a change to the product in order to be resolved. Most issues start as that customer-reported Issues that are reported by GitHub users external to the Azure organization. Auto-Assign Auto assign by bot Monitor labels Jan 17, 2025
@microsoft-github-policy-service microsoft-github-policy-service bot added the Azure CLI Team The command of the issue is owned by Azure CLI team label Jan 17, 2025
@yonzhan yonzhan added this to the Backlog milestone Jan 17, 2025
@yonzhan yonzhan removed the bug This issue requires a change to an existing behavior in the product in order to be resolved. label Jan 17, 2025
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 Azure CLI Team The command of the issue is owned by Azure CLI team customer-reported Issues that are reported by GitHub users external to the Azure organization. Monitor question The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Projects
None yet
Development

No branches or pull requests

3 participants