-
Notifications
You must be signed in to change notification settings - Fork 3.3k
[#114438129]address code analysis errors by pylints #17
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
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
src/azure/cli/_argparse.py
Outdated
Member
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.
This should be _display_usage
yugangw-msft
added a commit
that referenced
this pull request
Feb 29, 2016
[#114438129]address code analysis errors by pylints
| # For all codes, run 'pylint --list-msgs' or go to 'http://pylint-messages.wikidot.com/all-codes' | ||
| # C0111 Missing docstring | ||
| # C0103 Invalid %s name "%s" | ||
| # C0303 Trailing whitespace |
Contributor
Author
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.
We will do it in a separate PR to bring it back
yugangw-msft
added a commit
to yugangw-msft/azure-cli
that referenced
this pull request
Sep 22, 2017
yugangw-msft
added a commit
that referenced
this pull request
Sep 22, 2017
* Initial support for VM and single zone VMSS (#14) * wire up the initial zone support work * add output * add tests * disable package verifications * use a private copy of network sdk with zone support (#15) * Support for zoned public IP. Make global zone_type and zones_type. (#16) * Support for zoned public IP. Make global zone_type and zones_type. * Code review feedback. * apply api version range on vm zone test (#19) * show zone in the table output (#20) * install: support to build out a msi installer from local sources (#17) * doc:add command examples using availability zones (#21) * Installer: build debian bundle from a local clone (#28) * skip a few expeneive travis builds * test: update tests to work with new azure-mgmt-compute with zone support * network: support zone in network lb create (#37) * VNet peering examples. (#51) * Add BrazilUS and Dogfood cloud config files. (#50) * undo all changes specifically for private repository * fix help per review feedback * fix lint error * use newer nrp sdk version
DaeunYim
pushed a commit
to DaeunYim/azure-cli
that referenced
this pull request
Sep 12, 2020
Refactoring flexible server create
sturrent
added a commit
to sturrent/azure-cli
that referenced
this pull request
Oct 21, 2025
Three critical bugs were discovered and fixed that prevented User-Defined Route (UDR) analysis from functioning in the integrated CLI command: Bug Azure#17: RouteTableAnalyzer Not Integrated - RouteTableAnalyzer was copied but never instantiated in orchestrator - Added Phase 3 for route table analysis - Renumbered all phases from 1/8-8/8 to 1/9-9/9 - Embedded route_table_analysis into outbound_analysis['udr_analysis'] - Updated report_generator to accept route_table_analysis parameter Bug Azure#18: Route Table Field Case Sensitivity - Added dual checking for both 'vnetSubnetId' and 'vnet_subnet_id' - Ensures compatibility with different SDK data sources - Handles camelCase/snake_case variations robustly Bug Azure#19: Wrong Dictionary Key for Network Client - Fixed clients.get('network') → clients.get('network_client') - RouteTableAnalyzer was receiving None instead of NetworkManagementClient - This was the critical blocker preventing subnet lookups Testing Results: - aks-overlay cluster now correctly detects UDR with firewall route - Warning generated: "Default route (0.0.0.0/0) redirects all internet traffic through virtual appliance at 192.168.11.1" - Route table 'sec-udr' found and analyzed - Virtual appliance routes properly categorized Files Modified: - orchestrator.py: Added RouteTableAnalyzer integration, fixed client key - route_table_analyzer.py: Added dual-case field checking - report_generator.py: Added route_table_analysis parameter - PHASE6-PROGRESS.md: Documented all three bugs Impact: UDR analysis now fully functional, critical networking configurations are properly detected and reported.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.