Azure CLI v1 vs v2?How to manage Azure Backup with Azure Python SDK or Azure CliAzure RM: Logging in to CLI 1.0 using Azure AD applicationAzure CLI vs Powershell?Azure CLI how to check if a resource existsHow to stop a functionapp in a slot using azure CLIAzure CLI vs Python SDKazure cli failover groupsGetting SAS tokens in Azure CLIAzure CLI choose a option from a tablePowershell count azure CLI result

How to create a template with variable number of type parameters?

Some questions about Lightning and Tor

Can Russians naturally pronounce "попал в бесперспективняк"?

In Toy Story, are toys the only inanimate objects that become alive? And if so, why?

When do we use "no women" instead of "no woman"?

Is it safe for a student to give negative feedback in student evaluations?

How did Gollum know Sauron was gathering the Haradrim to make war?

How do you manage to study and have a balance in your life at the same time?

How Total raw is calculated for Science pack 2?

How to find better food in airports

Map a function that takes arguments in different levels of a list

Received email from ISP saying one of my devices has malware

Are there any writings by blinded and/or exiled Byzantine emperors?

Ways you can end up paying interest on a credit card if you pay the full amount back in due time

Order by inside subquery

How to fit Schwalbe Marathon Plus 28-622 on 622-16 rim

Why do we need explainable AI?

Is mathematics truth?

What are the French equivalents of "blow away the cobwebs"?

Why would a Intel 8080 chip be destroyed if +12 V is connected before -5 V?

Punishment in pacifist society

'Hard work never hurt anyone' Why not 'hurts'?

Blogging in LaTeX

Using GNU screen, I get raw prompt with backslashes



Azure CLI v1 vs v2?


How to manage Azure Backup with Azure Python SDK or Azure CliAzure RM: Logging in to CLI 1.0 using Azure AD applicationAzure CLI vs Powershell?Azure CLI how to check if a resource existsHow to stop a functionapp in a slot using azure CLIAzure CLI vs Python SDKazure cli failover groupsGetting SAS tokens in Azure CLIAzure CLI choose a option from a tablePowershell count azure CLI result






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








1















what are some of the advantages and disadvantage of using Azure CLI v2 over Azure CLI v1?



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.



However, are there any enhancements made specifically in v2 to make it more Resilient and Fast?










share|improve this question
























  • The Azure CLI v2 means Azure CLI while v1 means classic CLI. V2 is more recommended and works for ARM module. See Differences between Azure CLI products. The resource in ARM is more manageable and securable.

    – Charles Xu
    Mar 28 at 2:07

















1















what are some of the advantages and disadvantage of using Azure CLI v2 over Azure CLI v1?



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.



However, are there any enhancements made specifically in v2 to make it more Resilient and Fast?










share|improve this question
























  • The Azure CLI v2 means Azure CLI while v1 means classic CLI. V2 is more recommended and works for ARM module. See Differences between Azure CLI products. The resource in ARM is more manageable and securable.

    – Charles Xu
    Mar 28 at 2:07













1












1








1








what are some of the advantages and disadvantage of using Azure CLI v2 over Azure CLI v1?



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.



However, are there any enhancements made specifically in v2 to make it more Resilient and Fast?










share|improve this question














what are some of the advantages and disadvantage of using Azure CLI v2 over Azure CLI v1?



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.



However, are there any enhancements made specifically in v2 to make it more Resilient and Fast?







azure azure-cli azure-cli2






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Mar 28 at 1:52









explorerexplorer

3102 silver badges13 bronze badges




3102 silver badges13 bronze badges















  • The Azure CLI v2 means Azure CLI while v1 means classic CLI. V2 is more recommended and works for ARM module. See Differences between Azure CLI products. The resource in ARM is more manageable and securable.

    – Charles Xu
    Mar 28 at 2:07

















  • The Azure CLI v2 means Azure CLI while v1 means classic CLI. V2 is more recommended and works for ARM module. See Differences between Azure CLI products. The resource in ARM is more manageable and securable.

    – Charles Xu
    Mar 28 at 2:07
















The Azure CLI v2 means Azure CLI while v1 means classic CLI. V2 is more recommended and works for ARM module. See Differences between Azure CLI products. The resource in ARM is more manageable and securable.

– Charles Xu
Mar 28 at 2:07





The Azure CLI v2 means Azure CLI while v1 means classic CLI. V2 is more recommended and works for ARM module. See Differences between Azure CLI products. The resource in ARM is more manageable and securable.

– Charles Xu
Mar 28 at 2:07












1 Answer
1






active

oldest

votes


















2
















what are some of the advantages and disadvantage of using Azure CLI v2
over Azure CLI v1?




You can consider them as 2 different things.



Azure classic CLI(v1) is recommended for only the classic (Azure Service Manager) deployment. And Azure classic CLI is currently only planned to have support through the end of 2018.



But Azure CLI(v2) is designed for working with the Resource Manager deployment style. And it does not support ASM/Classic mode services




However, are there any enhancements made specifically in v2 to make it
more Resilient and Fast?




First, scripts are not compatible between both CLIs(v1 and v2).



Then some benefits of v2 is as following, you can also refer to this doc for more details:



1.Clean outputs for common workflows, such as you can use --out table , --out json, --out tsv



2.Improved command-line productivity:



You can use [tab][tab] to lookup parameters, including resource groups and names (only supported in BASH and BASH on Windows).



Work with either Azure resource ID values (--ids) or resource group and name (-g -n).



Built in client-side query engine powered by JMESPath






share|improve this answer
























    Your Answer






    StackExchange.ifUsing("editor", function ()
    StackExchange.using("externalEditor", function ()
    StackExchange.using("snippets", function ()
    StackExchange.snippets.init();
    );
    );
    , "code-snippets");

    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "1"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader:
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    ,
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );













    draft saved

    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55389042%2fazure-cli-v1-vs-v2%23new-answer', 'question_page');

    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    2
















    what are some of the advantages and disadvantage of using Azure CLI v2
    over Azure CLI v1?




    You can consider them as 2 different things.



    Azure classic CLI(v1) is recommended for only the classic (Azure Service Manager) deployment. And Azure classic CLI is currently only planned to have support through the end of 2018.



    But Azure CLI(v2) is designed for working with the Resource Manager deployment style. And it does not support ASM/Classic mode services




    However, are there any enhancements made specifically in v2 to make it
    more Resilient and Fast?




    First, scripts are not compatible between both CLIs(v1 and v2).



    Then some benefits of v2 is as following, you can also refer to this doc for more details:



    1.Clean outputs for common workflows, such as you can use --out table , --out json, --out tsv



    2.Improved command-line productivity:



    You can use [tab][tab] to lookup parameters, including resource groups and names (only supported in BASH and BASH on Windows).



    Work with either Azure resource ID values (--ids) or resource group and name (-g -n).



    Built in client-side query engine powered by JMESPath






    share|improve this answer





























      2
















      what are some of the advantages and disadvantage of using Azure CLI v2
      over Azure CLI v1?




      You can consider them as 2 different things.



      Azure classic CLI(v1) is recommended for only the classic (Azure Service Manager) deployment. And Azure classic CLI is currently only planned to have support through the end of 2018.



      But Azure CLI(v2) is designed for working with the Resource Manager deployment style. And it does not support ASM/Classic mode services




      However, are there any enhancements made specifically in v2 to make it
      more Resilient and Fast?




      First, scripts are not compatible between both CLIs(v1 and v2).



      Then some benefits of v2 is as following, you can also refer to this doc for more details:



      1.Clean outputs for common workflows, such as you can use --out table , --out json, --out tsv



      2.Improved command-line productivity:



      You can use [tab][tab] to lookup parameters, including resource groups and names (only supported in BASH and BASH on Windows).



      Work with either Azure resource ID values (--ids) or resource group and name (-g -n).



      Built in client-side query engine powered by JMESPath






      share|improve this answer



























        2














        2










        2










        what are some of the advantages and disadvantage of using Azure CLI v2
        over Azure CLI v1?




        You can consider them as 2 different things.



        Azure classic CLI(v1) is recommended for only the classic (Azure Service Manager) deployment. And Azure classic CLI is currently only planned to have support through the end of 2018.



        But Azure CLI(v2) is designed for working with the Resource Manager deployment style. And it does not support ASM/Classic mode services




        However, are there any enhancements made specifically in v2 to make it
        more Resilient and Fast?




        First, scripts are not compatible between both CLIs(v1 and v2).



        Then some benefits of v2 is as following, you can also refer to this doc for more details:



        1.Clean outputs for common workflows, such as you can use --out table , --out json, --out tsv



        2.Improved command-line productivity:



        You can use [tab][tab] to lookup parameters, including resource groups and names (only supported in BASH and BASH on Windows).



        Work with either Azure resource ID values (--ids) or resource group and name (-g -n).



        Built in client-side query engine powered by JMESPath






        share|improve this answer














        what are some of the advantages and disadvantage of using Azure CLI v2
        over Azure CLI v1?




        You can consider them as 2 different things.



        Azure classic CLI(v1) is recommended for only the classic (Azure Service Manager) deployment. And Azure classic CLI is currently only planned to have support through the end of 2018.



        But Azure CLI(v2) is designed for working with the Resource Manager deployment style. And it does not support ASM/Classic mode services




        However, are there any enhancements made specifically in v2 to make it
        more Resilient and Fast?




        First, scripts are not compatible between both CLIs(v1 and v2).



        Then some benefits of v2 is as following, you can also refer to this doc for more details:



        1.Clean outputs for common workflows, such as you can use --out table , --out json, --out tsv



        2.Improved command-line productivity:



        You can use [tab][tab] to lookup parameters, including resource groups and names (only supported in BASH and BASH on Windows).



        Work with either Azure resource ID values (--ids) or resource group and name (-g -n).



        Built in client-side query engine powered by JMESPath







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Mar 28 at 7:01









        Ivan YangIvan Yang

        7,8381 gold badge3 silver badges12 bronze badges




        7,8381 gold badge3 silver badges12 bronze badges





















            Got a question that you can’t ask on public Stack Overflow? Learn more about sharing private information with Stack Overflow for Teams.







            Got a question that you can’t ask on public Stack Overflow? Learn more about sharing private information with Stack Overflow for Teams.



















            draft saved

            draft discarded
















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid


            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.

            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55389042%2fazure-cli-v1-vs-v2%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            SQL error code 1064 with creating Laravel foreign keysForeign key constraints: When to use ON UPDATE and ON DELETEDropping column with foreign key Laravel error: General error: 1025 Error on renameLaravel SQL Can't create tableLaravel Migration foreign key errorLaravel php artisan migrate:refresh giving a syntax errorSQLSTATE[42S01]: Base table or view already exists or Base table or view already exists: 1050 Tableerror in migrating laravel file to xampp serverSyntax error or access violation: 1064:syntax to use near 'unsigned not null, modelName varchar(191) not null, title varchar(191) not nLaravel cannot create new table field in mysqlLaravel 5.7:Last migration creates table but is not registered in the migration table

            용인 삼성생명 블루밍스 목차 통계 역대 감독 선수단 응원단 경기장 같이 보기 외부 링크 둘러보기 메뉴samsungblueminx.comeh선수 명단용인 삼성생명 블루밍스용인 삼성생명 블루밍스ehsamsungblueminx.comeheheheh

            155 수학 과학 기타 둘러보기 메뉴eh추가해eh문서를 완성해