ui: show selected template hypervisor in deploy form - #13813
Conversation
022dbf3 to
171445b
Compare
4788654 to
3fefbb5
Compare
|
@shwstppr a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress. |
|
UI build: ✔️ |
3fefbb5 to
535dc17
Compare
|
Please build the exact current PR head for final validation: |
|
@Dogface2k a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress. |
|
UI build: ✔️ |
|
Validated exact head Using a real ready
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## 4.22 #13813 +/- ##
=========================================
Coverage 17.69% 17.70%
+ Complexity 15835 15831 -4
=========================================
Files 5925 5925
Lines 533539 533549 +10
Branches 65274 65277 +3
=========================================
+ Hits 94427 94482 +55
+ Misses 428435 428381 -54
- Partials 10677 10686 +9
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:
|

Summary
Fixes #13786.
Selecting a template could leave the Deploy VM form using the initial zone hypervisor. The displayed hypervisor and related form state could therefore be incorrect when the selected template used a different hypervisor.
The deploy form now follows the hypervisor metadata of the selected template.
Changes
Template deployment request behavior is unchanged. The fix updates the existing form state and does not add a separate hypervisor parameter to template deployment requests.
Validation
Validated exact head
535dc17c579cbed705e7f34e06a1d343fc446641against Apache4.22base532852824a9729ff9f073e3678d9d0bd8afeb059.