-
Notifications
You must be signed in to change notification settings - Fork 169
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
Adjust the NSG validation logic for GA #3356
Conversation
/azp run e2e |
No pipelines are associated with this pull request. |
/azp run "E2E - PullRequest" |
No pipelines are associated with this pull request. |
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.
LGTM
/azp run e2e |
Azure Pipelines successfully started running 1 pipeline(s). |
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.
LGTM
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.
LGTM
/azp run e2e |
Azure Pipelines successfully started running 1 pipeline(s). |
f0a2eb6
to
939047f
Compare
Which issue this PR addresses:
Fixes: ARO-2590
What this PR does / why we need it:
To adjust the validation logic of NSG validation for GA. Previously in private preview, we allow no nsgs to be attached to the subnets which the FP then assumes that the feature shouldn't be used. In GA, we make it explicit so that when the preconfigured nsg flag is enabled and no subnets are attached, the FP will error out instead.
Test plan for issue:
Unit tests.
Is there any documentation that needs to be updated for this PR?
no