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

[Network] az network lb create: Add warnings for default SKU #22339

Merged
merged 3 commits into from
May 11, 2022

Conversation

necusjz
Copy link
Member

@necusjz necusjz commented May 10, 2022

Related command

Description

In the latest profile and the profiles that use the same api-version as latest profile, the default public IP used for creation for an LB frontend with "az network lb create" and/or "az network lb frontend-ip create" will be changed from Basic to Standard. In advance of eventual breaking change, would like to add warning for users.

Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature


This checklist is used to make sure that common guidelines for a pull request are followed.

@necusjz necusjz added the Network - Load Balancer az network lb label May 10, 2022
@necusjz necusjz requested a review from jsntcy as a code owner May 10, 2022 07:41
@necusjz necusjz self-assigned this May 10, 2022
@ghost ghost requested a review from yonzhan May 10, 2022 07:41
@ghost ghost added Auto-Assign Auto assign by bot Network az network vnet/lb/nic/dns/etc... labels May 10, 2022
@yonzhan
Copy link
Collaborator

yonzhan commented May 10, 2022

Network

@necusjz necusjz merged commit 5a4a23d into Azure:dev May 11, 2022
@necusjz necusjz deleted the add-warnings branch May 11, 2022 06:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Auto-Assign Auto assign by bot Network - Load Balancer az network lb Network az network vnet/lb/nic/dns/etc...
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants