-
Notifications
You must be signed in to change notification settings - Fork 378
fix: Removing --costs parameter since it was removed in azqr v.3.0.0 (#1738) #1739
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
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -96,11 +96,6 @@ public override async Task<CommandResponse> ExecuteAsync(CommandContext context, | |
| var jsonReportFilePath = $"{reportFileName}.json"; | ||
| command += $" --output-name \"{reportFileName}\""; | ||
|
|
||
| // Azure Quick Review CLI can easily get throttle errors when scanning subscriptions with many resources with costs enabled. | ||
| // Unfortunately, getting such an error will abort the entire job and waste all the partial results. | ||
| // To reduce the chance of throttling, we disable costs reporting by default. | ||
| command += " --costs=false"; | ||
|
|
||
| // Also generate a JSON report for users who don't have access to Excel. | ||
| command += " --json"; | ||
|
Comment on lines
99
to
100
|
||
|
|
||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The CHANGELOG.md file needs to be updated to document this bug fix. According to the pre-merge checklist, product changes (bug fixes) must be documented in servers/Azure.Mcp.Server/CHANGELOG.md. This change fixes a bug where the azqr command would fail with version 3.0.0 or higher due to the removed --costs flag. Consider adding an entry under "Bugs Fixed" in the unreleased section documenting this fix and referencing issue #1738.