Skip to content

Conversation

@derekbekoe
Copy link
Member

The command returns 0 if successful, 1 otherwise.

@yugangw-msft
Copy link
Contributor

LGTM

yugangw-msft added a commit that referenced this pull request Feb 29, 2016
Load the python module in CI to catch import errors
@yugangw-msft yugangw-msft merged commit aa08d56 into Azure:master Feb 29, 2016
@derekbekoe derekbekoe deleted the ci-module-import-test branch February 29, 2016 18:02
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
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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants