-
Notifications
You must be signed in to change notification settings - Fork 4k
RemoteApp: RestartVm tenant admin cmdlet #717
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
Conversation
Can one of the admins verify this patch? |
Hi @Amarsi, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!
TTYL, AZPRBOT; |
@azuresdkci add to whitelist |
@Amarsi This is not early feedback, code complete for the 8/12 release was Friday. IUf your PR is not passing by Monday morning, it will not make the release. |
It came in very late for us and customer needs it desperately. |
@Amarsi please pull from "upstream dev" and update your fork |
I have found a bug, need to fix that. Also the MSI build is failing because the WindowsAzure.Management.RemoteApp.2.0.1 isn't signed. Need to publish the signed package. |
@Amarsi You need to fix the remote app library that the cmdlets are consuming so that is is signed - you will need to update azure-sdk-for-net, and republish with a new version, then update the version here |
Have updated the RemoteApp package and fixe the bug as well. |
redoing on demand run: http://azuresdkci.cloudapp.net/view/1-AzurePowerShell/job/powershell-on-demand/134/ |
@Amarsi Hi Amar, please resubmit this PR aginst the release branch (release-0.9.7). We will take it if you can have it submitted (and passing) today |
Submitted PR against release-0.9.7 branch |
@Amarsi closing in favor of the merged PR in release-0.9.7 - we will merge that back to the dev branch at the end of the release. |
Requires new version of RemoteApp management, WindowsAzure.Management.RemoteApp.2.0.1
Will not build as package isn't available yet
Sending for early feedback as this need to make 8/12 release