while reviewing rancher/ui#23993 i stumbled on a case where opening the pod logs
would cause an undefined error to crash the local ui server. `exec` is called
correctly from the `watchReconnect` observer which needs to happen first as it
parses the container name. If we call exec before we have a container name we
get an undefined error
When using an older vsphere node template in the latest version it was
possible that a user entered value would not be a valid option. When
the value isn't a valid option the dropdown has nothing selected. To
improve the UX we now notify the user that the current value is no
longer valid and sask them to select a new value.
rancher/rancher#23920
While working on a ticket to provide the ability to de-select subnetworks when
using the create subnetwork option I discovered the options were all messed up
and allowed you to misconfigure yourself into a hole.
I've moved ipalias and related networks settings out of advanced becuase
depending on what you select for your subnetwork the ability to choose ipalias
and the other settings changes.
This change allows you deselect a node subnet so you can create a subnetwork
automatically.
rancher/rancher#21079
We don't support the EdgeHTML browsers just like we don't support
Internet Explorer. I added EdgeHTML to the blacklist so that we will
display the unsupported page.
rancher/rancher#23909
while I was fixing another issue I looked at the page in FF and found that the
select styling was not inheriting correctly in dark theme so I dug around and
ended up needing to put in a workaround to ensure that the colors are inherited
correctly.
when I removed maybe-t helper I forgot to check grouped content in the
searchable select which was still looking for a translations. Moved the
translation lookup to the component when we generate the groupedContent so we
dont run into this issue again
rancher/rancher#23946
The backend has made a new implementation of creationType which allowed
me to remove the creationMethod concept and just use creationType.
This change allows us to properly populate the creation type form fields
when a user edits a vsphere nodetemplate.
rancher/rancher#23812
The keys for custom attributes needed to be unique. To enforce the
unique constraint I created the FormContextualKeyValue component.
This component behaves similarly to the FormContextualSelectArray
but handles key value pairs.
rancher/rancher#23782
While I was cleaning this up I found that groupByRef in cc this case did nothing
so I removed it. This exposed a bug in the sortable-table code where groupByRef
was coming back null but when we tried to get it, using embers getter, it would
fail because we passed a null value instead of an empty string.
Additionally I found that when using presorts we were continuously pushing into
the sort array on the component, which never gets reset, so I decided to clone
the array. We rarely use preSorts so it was never caught.
Additionally we never add/remove the descending key to our presorts so I've
added that. Without these when we pass the sort to embers sort we'd never
correctly sort any presorts based the descending flag.
rancher/rancher#23828
When editing a vsphere node template that used a RancherOS ISO
creation method it crashed the page due to an array not existing.
I also noticed that the tags, custom attributes and networks weren't
loading when editing so I resolved those issues too.
rancher/rancher#23796
Cody Jackson
Westly Wright
Westly Wright
Sylvia van Os
wj
loganhz
n313893254