Azure CLI curl package removed as default in 2.54.0

[kesava9]

Describe the bug

We have noticed that curl is missing in Azure CLI version 2.54.0 which is present in all previous versions as default.

This can be replicated using following github workflow :

name: AzureCLI
on:
  pull_request:
    branches:
      - main
jobs:
  check-cli-curl:
    runs-on: ubuntu-latest
    steps:
        
    - name: Add the runner
      uses: azure/CLI@v1
      with:
        azcliversion: 2.53.1
        inlineScript: |
          set -x
          IP=`curl https://api.ipify.org`
          echo "RUNNER_IP=$IP" >> $GITHUB_ENV
          
        
    - name: Add the runner
      uses: azure/CLI@v1
      with:
        azcliversion: 2.54.0
        inlineScript: |
          set -x
          IP=`curl https://api.ipify.org`
          echo "RUNNER_IP=$IP" >> $GITHUB_ENV

Related command

curl https://api.ipify.org

Errors

curl not found in latest version

Issue script & Debug output

NA

Expected behavior

It should return IP address

Environment Summary

2.54.0

Additional context

[yonzhan]

Thank you for opening this issue, we will look into it.

[mheskandari]

my azure ARM template for my apim has been failed with azure cli 2.54.0 which it had no issue up until now and I have to manually set the azure cli 2.53.1 in pipeline to keep it running . please do more tests before release dear Microsoft. these days I have to spend lots of time to find issues in pipeline which is not related to pipeline . they are happening only azure cli update!!!!!!

[bebound]

This is expected. Lots of packages are removed in image to reduce size. See #27567

You need to install them according to your own needs.

[kesava9]

Thanks @bebound , But, somehow its missing in release notes of latest version which is confusing or if I have missed it.

[mheskandari]

Thanks @bebound , But, somehow its missing in release notes of latest version which is confusing or if I have missed it.

yes that's true. during last couple months in each azure cli version I have been struggling with the pipelines. at least it needs to be documented

[sofbkeller]

I don't understand why a breaking change such as previously functional cmdlets inside of the az cli action should require someone to investigate why they stop working out of the blue. If someone is going to make a major change to functionality, why not do a version step? Some of us aren't developers and finding out why our pipeline broke is not fun.

[bebound]

It's in the release note

[BREAKING CHANGE] Remove unnecessary packages in docker image