When there was only one option we the add button was disabled and
we couldn't add the one option.
This change fixes it so that we can still select the single option if
desired.
rancher/rancher#23780
because we did not delay the readiness of the application when loading
translations when a user hit `update-setting` route we'd render the page before
the language had finished loading. Moving the language to the before model and
in the finally of the detect phase ensures we have our language loaded before we
remove the loading state and render the main content.
rancher/rancher#23776
I think the file it self may look more verbose as I've broken several of the
confusing portions into pure(ish) functions. I think this reduces the complexity
of the logic and makes it easier to read. Hopefully this will reduce the bugs
that keep cropping up.
We want to provide the owner as additional information when showing
node templates on the node templates page. We also want to make it so
that when selecting a node template the users templates will be grouped
and sorted to the top by default.
rancher/rancher#23325
When adding a github group to be an instio member we wanted the
appropriate Member Type to be displayed. We wanted 'Organization'
instead of 'group'.
We noticed that addAuthorizedPrincipal was being invoked with a newly
created member object instead of just passing the principal. Since
everything we could inspect code wise expected a principal instead
of a member I went ahead and just passed the principal.
rancher/rancher#23264
After pressing the 'create' button of the EKS driver the user was being
transitioned back to step 3 (Vpc & Subnet) rather than waiting on the
final page until the save is complete and returning to the cluster page.
An observer was being triggered by the save process which subsequently
set the step back to 3. To resolve this we will only enter the branch if
there are initialized values that need to be set back to default.
rancher/rancher#23493
-We now prepopulate fields as select component instead of just
free-form text fields.
-We added support for cloning from different sources.
-We also added support for custom attributes and tags.
To implement the above features we also added support for promise
based content for new-select and search-select and created a new
component contextual-select-array which provides a method for
filtering content based on previous selections.
rancher/rancher#21580
While editing a cluster properly support .x kube version comparisons when
filtering out cluster template revisions.
Coercing a .x version converts it to a .0 which made the revision look like
it was a kube downgrade. By making use of .satisfies when the revision
kube version ends with a '.x' we're now better able to check if the
kube version is a downgrade and filter appropriately.
rancher/rancher#23489
the check-override-allowed component did not know how to deal with the k8s
version question because of its tri state and how we deal with the patch version
that is an override but not really an override. I added a check to verify the
mode is view and we have the param then display param so we don't initialize the
form-version component which has logic to inject the current version into its
versions dropdown but only if we're new, editing, or cloning.
rancher/rancher#23478rancher/rancher#23465
The current kubernetes version wasn't being shown if it was no
longer a part of the supported versions when in view mode. Instead
the latest version was being displayed even if that wasn't what was
deployed. To resolve this we include the current version as one of
the choices if it's not present.
rancher/rancher#23465
We fixed a few deprecation for jquery on the cluster page but there were some
errors firing when using so I fixed the targeting.
There was also a intl error because of a missing api.
Due to some oddities in the way that Istio currently allows access to members to
the kiali and jaeger ui's we've decided to restrict the member search to groups
only. I've changed the verbiage on the lables to reflect this. Additionally I've
also exposed the searchOnlyGroups param on the principal search component. I did
not expose the user only param because this is not something we're normally
going to be doing.
rancher/rancher#23215
- Moved from Ember.$() to importing jquery.
- Moved from fn().on() to on(fn())
- Moved from fn().observes() to observer(fn())
This got /g/clusters from 27 warnings to 5 warnings for me.
Westly Wright
Cody Jackson
Westly Wright
loganhz
lvuch
Cody Jackson
n313893254