The open function in Python 2 returns IOError if the file doesn't exist. #20
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
Contributor
|
Looks good |
mayurid
added a commit
that referenced
this pull request
Feb 27, 2016
The open function in Python 2 returns IOError if the file doesn't exist.
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
sturrent
added a commit
to sturrent/azure-cli
that referenced
this pull request
Oct 21, 2025
- Modified RouteTableAnalyzer to accept VMSS analysis parameter - Updated _get_unique_subnet_ids() to extract subnet IDs from VMSS network profiles - Moved VMSS collection before Route Table analysis in orchestrator - Fixed subnet detection for clusters created without --vnet-subnet-id - Now correctly detects UDRs on both customer-provided and AKS-managed VNets - Changed progress display to use indentation instead of fractional step numbers (2.5/9 -> ' Collecting...') Test 2.4.4: Verified UDR detection on NAT Gateway cluster with managed VNet - Route table 'sec-udr' now correctly detected - Default route to virtual appliance (192.168.11.1) generates appropriate warnings - No regression on customer-provided VNet clusters (aks-overlay) Bug Azure#20 affects all AKS-managed VNet deployments (most common pattern). This fix enables UDR analysis for majority of AKS clusters.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.