PS cosmos db restore command: Skipping client side restore validation check

[dsapaliga]

Description

This is a simple fix to remove the validation check for restorable accounts when the customer uses the powershell restore command. Couple of reason for removing this:

• Due to the mismatch in location format given as input vs how we validate the permissions.
• Avoid timeout during this validation check for large account restores.

This change is already part of cli-preview, updating this for powershell stable now.

Mandatory Checklist

• Please choose the target release of Azure PowerShell. (⚠️Target release is a different concept from API readiness. Please click below links for details.)

  • General release
  • Public preview
  • Private preview
  • Engineering build
  • No need for a release

• Check this box to confirm: I have read the Submitting Changes section of CONTRIBUTING.md and reviewed the following information:

• SHOULD update ChangeLog.md file(s) appropriately
  • Update src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.
    • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header in the past tense.
  • Should not change ChangeLog.md if no new release is required, such as fixing test case only.
• SHOULD regenerate markdown help files if there is cmdlet API change. Instruction
• SHOULD have proper test coverage for changes in pull request.
• SHOULD NOT adjust version of module manually in pull request

[azure-client-tools-bot-prd]

Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status.

[Copilot]

Pull Request Overview

This PR removes client-side validation checks for restorable accounts in the PowerShell Cosmos DB restore command to address location format mismatches and prevent timeouts during large account restores.

• Removes the validation logic that checks if source accounts contain restorable resources for live accounts
• Eliminates the isSourceRestorableAccountDeleted variable and related conditional logic
• Streamlines the restore process by bypassing client-side validation that was causing issues

[dsapaliga]

Question for powershell team reviewers, how do i upgrade the version of this change? so, the customer would know which version to update to for this change to take efffect.

[YanaXu]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[YanaXu]

Question for powershell team reviewers, how do i upgrade the version of this change? so, the customer would know which version to update to for this change to take efffect.

Hi @dsapaliga, please update the changelog or the change will not be released.

[YanaXu]

The tests of this source code are skipped. Could you please test them and provide the test result?

[dsapaliga]

The tests of this source code are skipped. Could you please test them and provide the test result?

I have not found any reference to the DateTime.ToString(), my changes currently remove that section of code entirely, I have remove the skip from tests.

[dsapaliga]

@dsapaliga please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.

@microsoft-github-policy-service agree [company="{your company}"]

Options:

• (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.

@microsoft-github-policy-service agree

• (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.

@microsoft-github-policy-service agree company="Microsoft"

Contributor License Agreement

@microsoft-github-policy-service agree company="Microsoft"

[dsapaliga]

Question for powershell team reviewers, how do i upgrade the version of this change? so, the customer would know which version to update to for this change to take efffect.

Hi @dsapaliga, please update the changelog or the change will not be released.

Updated the changelog, please validate if it looks good, thank you.

[YanaXu]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[YanaXu]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[dsapaliga]

/azp run

[azure-pipelines]

Commenter does not have sufficient privileges for PR 28171 in repo Azure/azure-powershell

[YanaXu]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[YanaXu]

Hi @dsapaliga, let's handle the "skip" tests later. For this PR, please provide a screenshot of test, just let us know the result is OK.