-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Fixed and enhanced vlan field validation in the UI #10983
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
Fixed and enhanced vlan field validation in the UI #10983
Conversation
@DaanHoogland a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #10983 +/- ##
============================================
+ Coverage 16.57% 18.42% +1.84%
- Complexity 13868 16868 +3000
============================================
Files 5719 5951 +232
Lines 507178 599037 +91859
Branches 61571 90044 +28473
============================================
+ Hits 84085 110367 +26282
- Misses 413674 476872 +63198
- Partials 9419 11798 +2379
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
UI build: ✔️ |
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, verified the QA env.
Tested manipulating the start and end values of the VLAN, VxLAN and GRE ranges, looks good
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.
clgtm
Description
This PR fixes and enhances the validation of the values inserted in the VLAN/VNI field when configuring a new zone. Currently, it only checks if any of the fields are empty and if the range start value is greater than the range end value. Thus, it is possible to insert invalid values, as negatives.
With the PR changes, now the field validates if: any of the values is negative, any of the fields is empty or if the inserted values are inside the isolation method max and min values. The maximum and minimum values are now defined based on the selected isolation method (isolation method limits used can be find in the
NetworkServiceImpl
class). This PR also fixes a minor graphical issue, where the field displayed a red check icon, instead of a red error icon.Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Screenshots (if appropriate):
Before the changes:

After the changes:

How Has This Been Tested?
VLAN
VXLAN
GRE