Skip to content

[Azure Site Recovery] PR contains: aligning PowerShell to service object model, supporting some new features and some bug fixes. #2912

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 6 commits into from
Sep 15, 2016

Conversation

avneeshrai
Copy link

[Azure Site Recovery] Commit contains:

  1. Aligning PowerShell to service object model.
  2. Introducing deprecation warning for cmdlets and parameter sets to be deprecated in future.
  3. HUB changes.
  4. Bug Fixes.

1) Aligning PowerShell to service object model.
2) Introducing deprecation warning for cmdlets and parameter sets to be deprecated in future.
2) HUB changes.
3) Bug Fixes.
@cormacpayne
Copy link
Member

cormacpayne commented Sep 9, 2016

@avneeshrai Hey Avneesh, please merge the latest changes from dev to fix the conflicts #Resolved

@avneeshrai
Copy link
Author

avneeshrai commented Sep 9, 2016

@cormacpayne I have merged the latest changes from dev and resolved the conflicts. Please review and merge the PR. #Resolved

@avneeshrai
Copy link
Author

avneeshrai commented Sep 13, 2016

@markcowl Could you please review this PR. Given its a big PR I am expecting it to take some time of yours. #Resolved

@@ -22,7 +22,7 @@ namespace Microsoft.Azure.Commands.SiteRecovery
/// </summary>
[Cmdlet(VerbsCommon.Remove, "AzureRmSiteRecoveryNetworkMapping")]
[OutputType(typeof(ASRJob))]
public class RemoveAzureRMSiteRecoveryNetworkMapping : SiteRecoveryCmdletBase
Copy link
Contributor

@shahabhijeet shahabhijeet Sep 14, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

RemoveAzureRMSiteRecoveryNetworkMapping [](start = 17, length = 39)

Any reason the remove Networking mapping does not have SupportShouldProcess parameter? #Resolved

Copy link
Author

@avneeshrai avneeshrai Sep 14, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We get errors from the build infra for SupportShouldProcess parameter only if cmdlet has -Force parameter. I guess if Force is not present SupportShouldProcess is not mandatory as PR build succeeds. Please let me know if thats not the case.


In reply to: 78791145 [](ancestors = 78791145)

@shahabhijeet
Copy link
Contributor

shahabhijeet commented Sep 14, 2016

Overall looks good. Let's get the tests in to get decent coverage of your feature. #Resolved

@avneeshrai
Copy link
Author

Sure..i will update the PR with needed tests.


In reply to: 247099534 [](ancestors = 247099534)

@avneeshrai
Copy link
Author

Updated the PR after taking your comments and including new tests.


In reply to: 247124518 [](ancestors = 247124518,247099534)

@shahabhijeet shahabhijeet merged commit d7758b7 into Azure:dev Sep 15, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants