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
When editing both single and multi-cluster apps if you modified the
Template Version or the Target Projects and then cancelled it the
underlying store was still modified which then reflected those changes
on other pages like the single and multi-Cluster Apps pages.
To change this I cloned and nested the fields into a nested object named
'editable' and updated the primarySource on willSave for the relevant
targets subfield.
rancher/rancher#21228
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.
remove prototype extension
Remove translations from engines
The motivation behind this change stems from this issue ember-intl issues/797
and the current implmentation of engine support in ember-intl. The translations
essentially get bundled twice. Until ember-intl removes the second bundle it
makes sense to keep the translations in the main ui file.
Remove ember object and use regular object instead
Found durning upgrade to 3.12, I'm not sure why we'd even need to declare an
ember object for this return anyway.
Get the current cluster's id from scope servervice
Found durning upgrade to 3.12, not sure how this ever worked as I looked on live
and it was failing but the system didn't explode on 3.8. In 3.12
transistion.params is undefined and the whole system explodes. We were never
passing the queryparams so they wouldn't have come through. I changed this so we
fetched the current cluster id from the scope service and everything seems to
work correctly.
Ensure that accordion items only try to expand once during the init
Found durning upgrade to 3.12, expanded was being double rendered.
lint fix
test fixes
lint
project-member-row was using `avatarSrc` on its component which was slightly
different then the same code used in the principal model but really should have
been the same. I got rid of the duplicate code in the component since the model
is the data owner. It really should manage the avatar source building.
I also updated single quotes to doubles in template and refactored the owner
logic since it wasn't doing anything extra that the noUpdate flag was doing.
rancher/rancher#21440
We want to make it easier for someone that is managing multiple
clusters to see what template and template revision a cluster
is using. We also want to make it easy for a user to notice
that a cluster isn't using the latest revision.
To achieve this we added the template and revision to a column
in the clusters table to display both. We also indicate add
a warning badge beside a revision when the revision isn't
the latest.
rancher/rancher#22047
When a user upgraded there rancher install to >2.3 with clusters on now
unsupported versions of k8s we would show them the label that is used when
launching with a cluster template instead of the unsupported label
rancher/rancher#23085
When cloning a RKE template revision with overrides the values of the override
in the form were not reflected in the overrides section at the bottom of the
page because the alias on the question was never created.
rancher/rancher#23056
When viewing or cloning a template version the form-versions component would
select the derived version rather then the semver version the template was
created with. Now we will display the correct label or select the correct semver
version when in a view or clone of RKE templates.
rancher/rancher#23065
`Custom Cluster Overrides` was originally designed when we allowed users to
create custom overrides for items not in the UI but since that was removed the
template consumer will only ever see overrides for sections we have built in
and when launching we never display the overrides for ones with UI components.
rancher/rancher#23069
I saw this while fixing another issue, if initialized to false we set the
`enableLocalClusterAuthEndpoint` variable as such but that did not propigate
back up the model when in the init lifecycle. Rather than check the model we
should check the local param so we don't run in to these out of sync issues.
Tweaking a change made in rancher/ui#3376 to account for both cases. the fix
added would allow the case when deploying from a template but would break for
nontemplate launches when the value would be a bool again. Added a type check to
handle both cases.
The real fix should be changing the types in the `listquestions` api
where the data is being pulled from. The root cause exists there where the type
`boolean` is saved as a string.
rancher/rancher#22972
When consuming a cluster template selection of the template id from the drop
down didn't change the cluster template revision becuase the UI component was
using the readOnly value. Attached the selection to the correct value so the
action floats up (DDAU).
rancher/rancher#22977
Editing was failing when an existing unsupported storage type had
already been used and the ferature flag unsupported-storage-drivers
was false. Adding a volume as part of a workload was also broken
when attempting to use an unsupported storage type.
To remedy this I decided to refactor the code and make the filtering
happen explicitly only for the dropdowns.
I also decided to make feature checking reusable and either to use
by adding a service to check if a flag is enabled.
rancher/rancher#22895rancher/rancher#22998
When creating a cluster using a template localClusterAuthEndpoint was not
using the value provided by the template. The component assumed that
localClusterAuthEndpoint was a boolean when it was in fact a string that
represented a boolean. To resolve this a string comparison needed to
be made.
rancher/rancher#22972
While editing a cluster template when the template was shared with a
group the group was not visible under the Share Template section. We
needed to ensure that the group was visible.
The reason that this was occuring was because we weren't fetching the
principal for the group because we were only fetching when the
userPrincipalId was present and not when the groupPrincipalId was
present.
rancher/rancher#22971
When editing a cluster that was created with cluster template
the cluster template revision couldn't be saved.
The revisionId was stored as a component member variable instead
of as a part of the model. It needed to be stored as part of the
model in order for the NewOrEdit to see the changes and save
them. I went ahead and referenced the model directly everywhere
in the component and removed the component member variable.
rancher/rancher#22920
We want the user to be able to see the security options that were
selected even if they can't be edited when editing the cluster.
We had to extract and infer the selected options given the oauthScopes.
It would be better if our API could more closely reflect our fields.
rancher/rancher#19070
Adds the resource types "namespace", "cluster", "project" as
additional context to the titles of the respective deletion modals
in order to reduce the likelyhood of a user accidentally deleting
an unintented resource.
We changed the title from "Are you sure you want to delete" to
"Are you sure you want to delete the namespace:" with namespace
being bold. The same is true for cluster and project as well.
rancher/rancher#17619
Cody Jackson
Westly Wright
Westly Wright
loganhz
lvuch
Cody Jackson
n313893254
Vincent Fiduccia
loganhz
Gábor Lipták
rmweir