Pre-release: extract metadata generation logic and decouple from wheel 0.30.0

[wangzelin007]

Azure/azure-cli-extensions#7740

[Copilot]

Copilot reviewed 5 out of 6 changed files in this pull request and generated 2 comments.

Files not reviewed (1)

• HISTORY.rst: Language not supported

[wangzelin007]

Section title underlines should be at least as long as the text of the section title

[wangzelin007]

same as above

[AllyW]

It should be as what pkg_info.metadata_version is? like 2.2 now?

[AllyW]

Another more straightforward way to get pkgInfo is pkginfo.Wheel for dist-info or pkginfo.Develop for egg-info, as az extension list does in azure cli core here: https://github.com/Azure/azure-cli/blob/dev/src/azure-cli-core/azure/cli/core/extension/__init__.py#L154-L157

[jiasli]

I don't think it is a good idea to vendor code from wheel library. The code itself may become difficult to maintain.

Besides using pkginfo.Wheel as mentioned by #521 (comment), we may consider decoupling from wheel:

Solution 1: Define our own metadata in azext_metadata.json and add necessary fields, such as

{
    "azext.isPreview": false,
    "azext.minCliCoreVersion": "2.45.0"
    "azext.name": "ssh"
    "azext.description": "SSH into Azure VMs using RBAC and AAD OpenSSH Certificates"
    "azext.long_description": "SSH into Azure VMs using RBAC and AAD OpenSSH Certificates.  The client generates ..."
    ...
}

The content will be merged into metadata automatically:

azure-cli-dev-tools/azdev/operations/extensions/util.py

Lines 53 to 55 in 78af72c

	azext_metadata = _get_azext_metadata(ext_dir)
	if azext_metadata:
	metadata.update(azext_metadata)

https://github.com/Azure/azure-cli-extensions/blob/f19d4496d88cfb8ceb7e2115e280beb32b646091/src/index.json#L88209-L88211

                "metadata": {
                    "azext.isPreview": false,
                    "azext.minCliCoreVersion": "2.45.0",
                    "classifiers": [
                        "Development Status :: 4 - Beta",

Solution 2: Use regex to extract necessary information directly from setup.py and plug it into a template to generate index.json entries.

This way, we will no longer be affected by wheel's changes.