-
Notifications
You must be signed in to change notification settings - Fork 4k
Add Dedicated Host redeploy support #27764
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
base: main
Are you sure you want to change the base?
Conversation
Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please update md file following: https://dev.azure.com/msazure/AzureWiki/_wiki/wikis/AzureWiki.wiki/785403/Development-Workflow
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
@thomascoats please fix the 4 failed test cases
|
This PR was labeled "needs-revision" because it has unresolved review comments or CI failures. |
@msJinLei Hi, where can I find these logs for the failed test runs? Also, are these the same tests outlined in this documentation? https://dev.azure.com/msazure/AzureWiki/_wiki/wikis/AzureWiki.wiki/785405/Testing-and-Release |
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
![]() Please clicked the linked buttons here |
/azp run |
Commenter does not have sufficient privileges for PR 27764 in repo Azure/azure-powershell |
@msJinLei will tests rerun automatically? if not, could you trigger another run? the failing tests should be fixed now |
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
It cannot run automatically for now....Ping me to run it for you. |
Description
Adding parameter to Update-AzHost to support dedicated host redeploy
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.)
Check this box to confirm: I have read the Submitting Changes section of
CONTRIBUTING.md
and reviewed the following information:ChangeLog.md
file(s) appropriatelysrc/{{SERVICE}}/{{SERVICE}}/ChangeLog.md
.## Upcoming Release
header in the past tense.ChangeLog.md
if no new release is required, such as fixing test case only.