[dataprotection] Add 2026-06-01 API models for Elastic SAN backup/restore - #1083
Merged
Ethan Yang (necusjz) merged 1 commit intoSep 9, 2026
Merged
Conversation
…tore Add command models and mgmt-plane resource models for Microsoft.DataProtection API version 2026-06-01, covering the backup-instance create / validate-for-backup / validate-for-restore / restore trigger commands used by the Elastic SAN (eSAN) datasource. The 2026-06-01 backupInstances model adds the resourceSelectors property on GenericBackupDatasourceParameters required by eSAN backup/restore.
3 tasks
Priyansh Choudhary (priyansh17)
pushed a commit
to priyansh17/azure-cli-extensions
that referenced
this pull request
Sep 8, 2026
…r aaz reproducibility (eSAN) The eSAN change hand-edited the api-version and resource_selectors in these aaz-generated commands but left the _aaz_info version metadata stale, so regenerating reverted the customizations. Regenerate create/update/validate-for-backup/validate-for-restore/restore-trigger from the 2026-06-01 command model (Azure/aaz#1083) so _aaz_info, api-version, and schema are consistent and the commands reproduce cleanly. No runtime change for create/validate/restore (already called 2026-06-01); update moves 2026-03-01 to 2026-06-01 where resource_selectors is valid.
Ethan Yang (necusjz)
approved these changes
Sep 9, 2026
Ethan Yang (necusjz)
pushed a commit
to Azure/azure-cli-extensions
that referenced
this pull request
Sep 9, 2026
* [DATAPROTECTION] Add AzureElasticSAN support: update HISTORY, manifest, and command configurations * [DATAPROTECTION] Enhance AzureElasticSAN support: add configuration and restore scripts, update permissions, and refine help documentation * [DATAPROTECTION] Enhance AzureElasticSAN support: update README for restore request, add JSON validation in backup initialization, and implement tests for backup/restore configurations * [DATAPROTECTION] Add AzureElasticSAN support: update HISTORY, modify API version for backup/restore, enhance validation, and implement tests for backup/restore workflows * [DATAPROTECTION] Update AzureElasticSAN support: refine backup and restore configurations, enhance help documentation, and improve error handling * [DataProtection] Update backup-instance test recordings for api-version 2026-06-01 bump The eSAN change bumped backup-instance create/update/validate-for-backup/validate-for-restore/restore-trigger operations to api-version=2026-06-01. Update the recorded request URIs in the 8 affected backup-instance cassettes so VCR playback matches the version the CLI now sends; polling, show, delete and non-bumped operations are left at their recorded versions. * [DataProtection] Make blob client lazy in initialize-backupconfig so non-blob datasource types don't require az login The initialize-backupconfig command was registered with client_factory=cf_blob_container_mgmt, which eagerly builds a storage management client (requiring an authenticated account) before the handler runs. This made AzureElasticSAN/AzureKubernetesService unit tests fail with 'Please run az login'. Build the blob client lazily inside the AzureBlob/AzureDataLakeStorage branch only when --include-all-containers is used, so eSAN/AKS paths no longer require login. * docs: update TODO comment with owner information for RBAC guidance on Elastic SAN backup/restore * [DataProtection] Regenerate backup-instance commands at 2026-06-01 for aaz reproducibility (eSAN) The eSAN change hand-edited the api-version and resource_selectors in these aaz-generated commands but left the _aaz_info version metadata stale, so regenerating reverted the customizations. Regenerate create/update/validate-for-backup/validate-for-restore/restore-trigger from the 2026-06-01 command model (Azure/aaz#1083) so _aaz_info, api-version, and schema are consistent and the commands reproduce cleanly. No runtime change for create/validate/restore (already called 2026-06-01); update moves 2026-03-01 to 2026-06-01 where resource_selectors is valid. --------- Co-authored-by: Priyansh Choudhary <choudharypr@microsoft.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds the
2026-06-01DataProtection API command models for the Azure Elastic SAN (eSAN) backup/restore onboarding, keeping the aaz command models in sync with the changes made in the azure-cli-extensionsdataprotectionextension (Azure/azure-cli-extensions#9938).What changed
Adds
2026-06-01version sections + resource models for the backup-instance operations that the eSAN feature bumped to the GA2026-06-01API:backup-instance create(backupInstances/{}PUT) — now carriesGenericBackupDatasourceParameters.resourceSelectors(the eSAN volume selectors)backup-instance validate-for-backup(backupVaults/{}/validateForBackup)backup-instance validate-for-restore(backupInstances/{}/validateRestore)backup-instance restore trigger(backupInstances/{}/restore)Per the standard aaz pattern, adding the
backupInstances/{}resource version also appends a### [2026-06-01]section to the siblingdelete/show/updatecommands of that resource; the extension independently pins those commands to their existing versions (same as the prior2026-03-01autoprotection PR #993).Why
The eSAN extension changes hand-edited the aaz-generated code (api-version bump +
resourceSelectors). Syncing them here ensures future regenerations reproduce these customizations instead of engineers re-creating them from scratch.Validation
aaz-dev command-model verifypasses (models consistent).resourceSelectorspresent in the new2026-06-01create model; absent in2026-03-01(confirms it is new to2026-06-01).