{Storage}: Add None version for ResourceType.DATA_STORAGE_TABLE#31670
{Storage}: Add None version for ResourceType.DATA_STORAGE_TABLE#31670
Conversation
… requires it in extension
️✔️AzureCLI-FullTest
|
|
Hi @calvinhzy, |
️✔️AzureCLI-BreakingChangeTest
|
|
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 adds support for a “None” API version for the DATA_STORAGE_TABLE resource type so that calling get_sdk will succeed for this resource.
- Introduces
ResourceType.DATA_STORAGE_TABLE: Nonein the default API version mapping - Ensures extensions relying on
get_sdkcan handle table storage
Comments suppressed due to low confidence (2)
src/azure-cli-core/azure/cli/core/profiles/_shared.py:221
- Add a unit test that verifies
default_api_version(ResourceType.DATA_STORAGE_TABLE)returnsNone, ensuring this new mapping is covered by automated tests.
ResourceType.DATA_STORAGE_TABLE: None,
src/azure-cli-core/azure/cli/core/profiles/_shared.py:221
- [nitpick] Consider updating the
default_api_versiondocstring or adding an inline comment to clarify whyDATA_STORAGE_TABLEis set toNonefor maintainability.
ResourceType.DATA_STORAGE_TABLE: None,
Related command
Description
Add None version for ResourceType.DATA_STORAGE_TABLE as using get_sdk requires it in extension for Azure/azure-cli-extensions#8878
The reason that the value is None is because get_sdk() by default will search for parent folder with the version number unless this specific value of None is provided, and the DATA_STORAGE_TABLE package is single-api, therefore having no parent folder with a version number.
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.