Remove ad-hoc api versions
See original GitHub issueSeveral command modules use ad-hoc api versions for azure-mgmt-network
SDK (https://github.com/Azure/azure-cli/pull/17816):
These API versions are preserved when trimming the azure-mgmt-network
SDK:
This leads to bigger Azure CLI package.
The solution is to migrate to the latest API version:
Issue Analytics
- State:
- Created a year ago
- Comments:9 (9 by maintainers)
Top Results From Across the Web
Remove ad-hoc api versions · Issue #23389 · Azure/azure-cli · GitHub
Several command modules use ad-hoc api versions for azure-mgmt-network SDK (#17816): ... Let's remove them in the coming breaking change window.
Read more >Delete Version—ArcGIS REST APIs
Delete a version from an enterprise geodatabase. ... Versioning endpoints in this API, including Create Version, Reconcile Version, and Delete Version, ...
Read more >3.2 - 3.7 - REST API Designer - Ad Hoc Assignee
3.2 - 3.7 - REST API Designer - Ad Hoc Assignee. Version: 3.8; 3.7; 3.6; 3.5; 3.4; 3.3; 3.2. Please rate how useful...
Read more >API Versioning - CyberArk Docs
This section explains how to specify which REST API version you intend to implement. API versioning is supported from Privileged Access Security v10.6....
Read more >'Quick and Dirty' – ad-hoc ways of GETting data from Azure ...
... Some times there is ad-hoc need to get data from Azure Management API, ... and some other headers removed (works for approx...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
vm_default_target_network: @zhoxing-ms nw_connection_monitor: @necusjz container_network: @joseph-porter appservice_network, appservice_ensure_subnet: @panchagnula
@panchagnula as I recall, this was to force to a newer API when this was developed as the “default” did not support delegations. This should not be a problem now.