Skip to content
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

Add HubRoutingPreference as an optional command in New-AzRouteServer and Update-AzRouteServer #18252

Conversation

yeliMSFT
Copy link
Contributor

@yeliMSFT yeliMSFT commented May 19, 2022

Description

Add HubRoutingPreference as an optional command in New-AzRouteServer and Update-AzRouteServer commands

Checklist

  • I have read the Submitting Changes section of CONTRIBUTING.md
  • The title of the PR is clear and informative
  • The appropriate ChangeLog.md file(s) has been updated:
    • For any service, the ChangeLog.md file can be found at src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md
    • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header -- no new version header should be added
  • The PR does not introduce breaking changes
  • If applicable, the changes made in the PR have proper test coverage
  • For public API changes to cmdlets:

@yeliMSFT yeliMSFT requested a review from MikhailTryakhov as a code owner May 19, 2022 22:22
@ghost ghost added the customer-reported label May 19, 2022
@ghost
Copy link

ghost commented May 19, 2022

Thank you for your contribution yeliMSFT! We will review the pull request and get back to you soon.

@ghost
Copy link

ghost commented May 19, 2022

CLA assistant check
All CLA requirements met.

@VeryEarly
Copy link
Contributor

/azp run

@VeryEarly VeryEarly self-assigned this May 23, 2022
@azure-pipelines
Copy link
Contributor

Azure Pipelines successfully started running 3 pipeline(s).

@VeryEarly VeryEarly merged commit 585b2bb into Azure:network-2022-01-01 May 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants