-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Azure CLI Task is emitting a lot of log output #15970
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
Comments
I agree entirely. I came looking for info on this behaviour as well. I found this closed issue from last year: #14156. It has a not-ideal workaround in it but no fix. Any chance this behaviour could be revisited? My environment have over 100 subscriptions in it so this makes the logs for each AzureCLI@2 task an absolute mess. |
I've come across this issue too and attempted to change the code to facilitate hiding extra output: #16701. |
This issue is stale because it has been open for 180 days with no activity. Remove the stale label or comment on the issue otherwise this will be closed in 5 days |
There is no harm in reducing the log size to make everyone life less difficult. @jhueppauff Please remove the stale label. |
This issue is stale because it has been open for 180 days with no activity. Remove the stale label or comment on the issue otherwise this will be closed in 5 days |
Type: Question (maybe a feature request)
Enter Task Name: AzureCLI
Environment
Azure Pipelines - affects all accounts
Hosted agent and private agent
Issue Description
I am using the AzureCLI Task in a pipeline to build bicep files.
The task emits an unnecessary amount of output which makes it harder to catch the important and "real" log output.
As far as I can tell it runs az --version which takes about 20 lines and then it prints out every subscription it seems to have access to. Which in my case adds 60 lines of output.
The only output the inline script produces (when everything goes right) is 0.
It feels a bit wrong to print out so much unnecessary information and it makes it hard to catch the important stuff.
Is there any option to reduce the amount of log output?
The text was updated successfully, but these errors were encountered: