Allow selecting network for VNF nics if template nics > 0 and is a non deploy-as-is template#13423
Allow selecting network for VNF nics if template nics > 0 and is a non deploy-as-is template#13423Pearl1594 wants to merge 2 commits into
Conversation
…n-deploy as is template
nvazquez
left a comment
There was a problem hiding this comment.
Code LGTM thanks @Pearl1594
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## 4.22 #13423 +/- ##
============================================
- Coverage 17.67% 17.67% -0.01%
Complexity 15792 15792
============================================
Files 5922 5922
Lines 533165 533180 +15
Branches 65208 65218 +10
============================================
+ Hits 94242 94244 +2
- Misses 428276 428290 +14
+ Partials 10647 10646 -1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
@Pearl1594
|
|
thanks @Pearl1594 for the info I can reproduce the issue. the fix could be as simple as 🤦 |
Oh yeah |
|



Description
This PR fixes an issue where we can't select the network for VNF nic mapping if there are template nics and it's a non deploy-as-is VNF template
introduced by: #12499
Types of changes
Feature/Enhancement Scale or Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?
How did you try to break this feature and the system with this change?