[fleet] upgrade fleet sdk to 2024-05-02-preview

[pdaru]

---

This checklist is used to make sure that common guidelines for a pull request are followed.

Related command

General Guidelines

• [ ] Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
• [ ] Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)
• [ ] My extension version conforms to the Extension version schema

For new extensions:

• [ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish

There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

[azure-client-tools-bot-prd[bot]]

️✔️Azure CLI Extensions Breaking Change Test

>

>

️✔️Non Breaking Changes

> > >

[azure-client-tools-bot-prd[bot]]

Hi @pdaru, Please write the description of changes which can be perceived by customers into HISTORY.rst. If you want to release a new extension version, please update the version in setup.py as well.

[azure-client-tools-bot-prd[bot]]

Hi @pdaru, Since the current milestone time is less than 7 days, this pr will be reviewed in the next milestone.

[yonzhan]

fleet

[github-actions[bot]]

:warning: Release Suggestions

Module: fleet

• :warning: Please update VERSION to be 1.1.3 in src/fleet/setup.py

  Notes

• Stable/preview tag is inherited from last release. If needed, please add stable/preview label to modify it.
• Major/minor/patch/pre increment of version number is calculated by pull request code changes automatically. If needed, please add major/minor/patch/pre label to adjust it.
• For more info about extension versioning, please refer to Extension version schema

[pdaru]

I'm not sure how/why it made changes to amg dir. Individual commits suggest no changes to those files.

[pdaru]

$ azdev style fleet

=============== | Style Check |

extension(s): [ fleet ] installed from a wheel may need --include-whl-extensions option

unsure how to resolve this.

@kairu-ms please could you help resolve the 2 issues?

[kairu-ms]

I'm not sure how/why it made changes to amg dir. Individual commits suggest no changes to those files.

You can revert back the change in amg folder

[kairu-ms]

$ azdev style fleet

===============

| Style Check | extension(s): [ fleet ] installed from a wheel may need --include-whl-extensions option

unsure how to resolve this.

@kairu-ms please could you help resolve the 2 issues?

You should install it from source code instead of wheel. Please uninstall it by az extension remove --name fleet first. Then use azdev extension add fleet to install from your source code.