{CI} Ship .yaml test fixtures in azure_cli_fulltest wheel#33437
{CI} Ship .yaml test fixtures in azure_cli_fulltest wheel#33437naga-nandyala wants to merge 1 commit into
Conversation
Add *.yaml and **/*.yaml to package_data in scripts/ci/build.sh so non-recording fixtures (e.g. acr/tests/latest/taskfilesample.yaml) are included in the ephemeral azure_cli_fulltest wheel installed by TestRpmPackagesAzureLinux. Fixes test_acr_task FileNotFoundError after #33135 removed its @live_only decorator.
️✔️AzureCLI-FullTest
|
|
Hi @naga-nandyala, |
❌AzureCLI-BreakingChangeTest
Please submit your Breaking Change Pre-announcement ASAP if you haven't already. Please note:
|
|
Thank you for your contribution! We will review the pull request and get back to you soon. |
|
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). pip install azdev --upgrade
azdev setup -c <your azure-cli repo path> -r <your azure-cli-extensions repo path>
|
There was a problem hiding this comment.
Pull request overview
This PR updates the CI-built azure-cli-fulltest wheel packaging rules so YAML-based test fixtures are included in the wheel, preventing fixture FileNotFoundErrors when tests run from the installed artifact.
Changes:
- Add
*.yamltopackage_dataso top-level YAML fixtures in test packages are included. - Add recursive
**/*.ymland**/*.yamlpatterns to include YAML fixtures in nested subdirectories of test packages.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Add .yaml and **/.yaml to package_data in scripts/ci/build.sh so non-recording fixtures (e.g. acr/tests/latest/taskfilesample.yaml) are included in the ephemeral azure_cli_fulltest wheel installed by TestRpmPackagesAzureLinux. Fixes test_acr_task FileNotFoundError after #33135 removed its @live_only decorator.
Related command
Description
Testing Guide
History Notes
[Component Name 1] BREAKING CHANGE:
az command a: Make some customer-facing breaking change[Component Name 2]
az command b: Add some customer-facing featureThis checklist is used to make sure that common guidelines for a pull request are followed.
The PR title and description has followed the guideline in Submitting Pull Requests.
I adhere to the Command Guidelines.
I adhere to the Error Handling Guidelines.