Add migration cmdlets

[DeepakRajendranMsft]

No description provided.

[azurecla]

Hi @DeepakRajendranMsft, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
We will now validate the agreement and then real humans will evaluate your PR.

TTYL, AZPRBOT;

[DeepakRajendranMsft]

@markcowl, CI is good now :)

[cormacpayne]

On demand: http://azuresdkci.cloudapp.net/view/1-AzurePowerShell/job/powershell-demand/1072/

[haitch]

it failed with this test (same test failed in my PR also), someone should fix this test
Microsoft.WindowsAzure.Commands.Test.Websites.SaveAzureWebsiteLogTests.SaveAzureWebsiteLogWithNoFileExtensionTest

[markcowl]

SupportsShouldProcess=true

[DeepakRajendranMsft]

@markcowl why do you think we need ShouldProcess() here? we do not need any confirmation of sorts from the user?

@DeepakRajendranMsft This is required for all new cmdlets. ShouldProcess does not normally print a prompt; it just allows the user to use -Confirm and -WhatIf to cotnrol / reflect over execution of the cmdlet.

@markcowl These cmdlets are not “new-” cmdlets. These are similar to Move-Azurestorage, and so I don’t believe we need ShouldProcess for these Move- cmdlets.

@DeepakRajendranMsft It is the same for substantially changed cmdlets, like these. If these are a major new set of cmdlets for migrating resources, we want to make sure that they are following best practices

[markcowl]

Do not pass -Confirm

Yep. just fixed that. :)

[markcowl]

@DeepakRajendranMsft It looks like you added the -Confirm parameter to each of your cmdlet invocatiosn in script. -Confirm tells the cmdlet to always prompt on ShouldProcess. Remove this parameter and these issues should go away

@markcowl yep, just fixed that

[cormacpayne]

On demand: http://azuresdkci.cloudapp.net/view/1-AzurePowerShell/job/powershell-demand/1085/

[DeepakRajendranMsft]

@markcowl @cormacpayne are we good for the merge?