简体   繁体   English

Azure CLI v1与v2?

[英]Azure CLI v1 vs v2?

what are some of the advantages and disadvantage of using Azure CLI v2 over Azure CLI v1? 与Azure CLI v1相比,使用Azure CLI v2有哪些优点和缺点?

I have searched various articles online. 我在网上搜索了各种文章。 Sounds like Azure CLI v2 is more developer friendly, built on python and provides auto complete capabilities and works well with linux POSIX tools. 听起来Azure CLI v2对开发人员更友好,它基于python构建,并提供自动完成功能,并且可以与linux POSIX工具一起很好地工作。

However, are there any enhancements made specifically in v2 to make it more Resilient and Fast? 但是,v2是否有专门增强的功能,使其更具弹性和速度?

what are some of the advantages and disadvantage of using Azure CLI v2 over Azure CLI v1? 与Azure CLI v1相比,使用Azure CLI v2有哪些优点和缺点?

You can consider them as 2 different things. 您可以将它们视为2种不同的事物。

Azure classic CLI(v1) is recommended for only the classic (Azure Service Manager) deployment. 建议仅对经典(Azure Service Manager)部署使用Azure经典CLI(v1)。 And Azure classic CLI is currently only planned to have support through the end of 2018. 而且,Azure经典CLI目前仅计划在2018年底之前提供支持。

But Azure CLI(v2) is designed for working with the Resource Manager deployment style. 但是Azure CLI(v2)设计用于使用资源管理器部署样式。 And it does not support ASM/Classic mode services 而且它不支持ASM /经典模式服务

However, are there any enhancements made specifically in v2 to make it more Resilient and Fast? 但是,v2是否有专门增强的功能,使其更具弹性和速度?

First, scripts are not compatible between both CLIs(v1 and v2). 首先,两个CLI(v1和v2)之间的脚本不兼容。

Then some benefits of v2 is as following, you can also refer to this doc for more details: 然后v2的一些好处如下,您还可以参考此文档以获取更多详细信息:

1.Clean outputs for common workflows, such as you can use --out table , --out json, --out tsv 1,清理常见工作流程的输出,例如可以使用--out table,--out json和--out tsv

2.Improved command-line productivity: 2.提高命令行生产力:

You can use [tab][tab] to lookup parameters, including resource groups and names (only supported in BASH and BASH on Windows). 您可以使用[tab] [tab]查找参数,包括资源组和名称(仅Windows的BASH和BASH支持)。

Work with either Azure resource ID values (--ids) or resource group and name (-g -n). 使用Azure资源ID值(--ids)或资源组和名称(-g -n)。

Built in client-side query engine powered by JMESPath 内置由JMESPath支持的客户端查询引擎

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM