Fixed environment-scenario and component-scenario tests

[lavakumarrepala]

---

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]

️✔️Azure CLI Extensions Breaking Change Test

️✔️Non Breaking Changes

[azure-client-tools-bot-prd]

Hi @lavakumarrepala,
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.

[yonzhan]

Thank you for your contribution! We will review the pull request and get back to you soon.

[github-actions]

The git hooks are available for azure-cli and azure-cli-extensions repos. They could help you run required checks before creating the PR.

Please sync the latest code with latest dev branch (for azure-cli) or main branch (for azure-cli-extensions).
After that please run the following commands to enable git hooks:

pip install azdev --upgrade
azdev setup -c <your azure-cli repo path> -r <your azure-cli-extensions repo path>

[github-actions]

• For more info about extension versioning, please refer to Extension version schema

[Copilot]

Pull request overview

This PR updates the azext_mlv2 live scenario tests and their VCR recordings for environment- and component-related commands, aiming to fix failing registry/workspace scenario runs by aligning test inputs and refreshing recordings.

Changes:

• Updated environment registry scenario commands/assertions to target different registry assets and normalized registry name casing (testFeed → testfeed).
• Updated component registry scenario commands/assertions to use the dsvm-test registry and relaxed list-size assertions.
• Refreshed multiple test recordings to reflect current service responses, CLI/SDK versions, and workspace/registry endpoints.

Reviewed changes

Copilot reviewed 12 out of 14 changed files in this pull request and generated 6 comments.

Show a summary per file

File	Description
src/machinelearningservices/azext_mlv2/tests/latest/test_environment_scenarios.py	Updates registry environment show/create/archive test commands and expectations.
src/machinelearningservices/azext_mlv2/tests/latest/test_component_scenarios.py	Updates component registry tests and introduces per-run component naming in test_component.
src/machinelearningservices/azext_mlv2/tests/latest/recordings/test_environment_show_registry.yaml	Updates recording for environment show in registry (discovery + show call).
src/machinelearningservices/azext_mlv2/tests/latest/recordings/test_environment_create_in_registry.yaml	Updates recording for creating environments in a registry (including LRO polling).
src/machinelearningservices/azext_mlv2/tests/latest/recordings/test_environment_archive_in_registry.yaml	Updates recording for archiving an environment version in a registry.
src/machinelearningservices/azext_mlv2/tests/latest/recordings/test_create_pipeline_component.yaml	Updates recording for creating/listing a pipeline component in a workspace.
src/machinelearningservices/azext_mlv2/tests/latest/recordings/test_component_with_short_resource_id.yaml	Updates discovery recording for component creation failure case in registry.
src/machinelearningservices/azext_mlv2/tests/latest/recordings/test_component_show_without_version_label.yaml	Updates discovery recording for component show error case in registry.
src/machinelearningservices/azext_mlv2/tests/latest/recordings/test_component_show_registry.yaml	Updates recording for component show in registry.
src/machinelearningservices/azext_mlv2/tests/latest/recordings/test_component_list_registry.yaml	Updates recording for listing component versions in registry.
src/machinelearningservices/azext_mlv2/tests/latest/recordings/test_component_archive_registry.yaml	Updates recording for archiving a component version in registry.
src/machinelearningservices/azext_mlv2/tests/latest/recordings/test_component_restore_registry.yaml	Updates recording for restoring a component version in registry.

Comments suppressed due to low confidence (1)

src/machinelearningservices/azext_mlv2/tests/latest/recordings/test_environment_show_registry.yaml:71

• This recording captures a 404 Not Found for the environment show request, but the test asserts a successful payload with id/name. Update/re-record the cassette to capture a successful (2xx) response for an existing environment version, or adjust the test to expect an error.

    method: GET
    uri: https://cert-int.experiments.azureml-test.net/mferp/managementfrontend/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/000000000000000/providers/Microsoft.MachineLearningServices/registries/testfeed/environments/000000000000000/versions/93435847-704b-4280-83f3-f735d8b5eff7?api-version=0000-00-00
  response:
    body:
      string: '{"error": {"code": "UserError", "message": "Could not find asset with

[wangzelin007]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).