rancher/rancher#23452
expose link-to new-group route
Translations change and move static property (convention)
Refactor form-global-roles
Refactor such that user and group are optional parameters. Adds
groupPrincipalId. Destructure smarter so that users are not required for the
mapper function to work. Move bindings to own init. Refactor make to recognize
groups. Translations changes.
Add cru-group-account component
This component does not actually create a group but a global-role-binding with a
groupPrincipalId instead of a userId. Perhaps cru-global-role-binding would work
but in the future this component can and probably will be adapted to create
local groups as well, so the name would fit. At that point the component could
also be refactored to work for the add user page because at that point pretty
much doing the same thing but that is not with-in the scope of this change.
Currently the componet is expected to be used with an auth provider that
supports groups which is why it does not also create the group. This should be
taken into consideration if we ever update this to work with local groups.
Translations changes.
formatting
wip
Add tab nav template only component
rename users index route -> users & add groups route
get groups from grb list and build groupPrincipal list
Add role binding to the fetched group principal
Add account-group-row component and define table row views
global role binding with group edit page
Fix transitionTo in cancel and doneSaving -> cru-group-account
translations
Add initialPrincipal param to input-identity to allow use on edit
reduce duplicate principal calls and display on groups list page
fix role links types from account-group-row
add group delete functionality
translations and bulk action fix
sort global role names in modal and row
delete GRB modal translations
move users route to security-> users, break out groups route security
remove unneeded component
Live update fixes
translation fix
fix broken link to old accounts route
remove unneeded props, angle bracket components, general cleanup
lint fixes
Change add group button
Add warning on add group for non-local auth only and translations
Remove warning from delete group modal and change translations
re-org form-global-roles display
breaks the display out into base|user-custom|additional roles
adds back in details & descriptions
fixes role ids in translations file
`templateChanged` which loads the content of what we need for a MC app was
updated to watch a new property, `editable: { selectedTemplateUrl } `. The new
property was declared on the component as a object. Observers watching a static
object and that have never been fetched do not recompute. If we set the property
on init to the object it would have been declared with then additional sets on
the watched property cause the observer to recompute.
rancher/rancher#24057
The backend was setting the default to legacy so that the legacy
template would still work when users migrate to the latest
version of the driver. This was causing the default value to
be legacy when creating a new vsphere template. Forcing
the backend to change the default will likely lead to problems
with the migration so we're making the change on the front end.
Ultimately we use the existing set default logic if a vsphere template
is being created (as opposed to edited) instead of just when the
creation type doesn't exist or is invalid.
We also changed the text for the legacy value to be friendlier.
rancher/rancher#24060
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
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
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
creationType was using the wrong values after refactoring to
combine two dropdowns into one. I renamed the existing
config.creationType to creationMethod and now observe
creationMethod to properly set config.creationType.
When global roles were added the front end had to make some assumptions for
non-admin users to ensure the user had login access. This role used to be hidden
but was made visible by default. With this exposed we now check before save if
the user has some kind of login access and throw an error if not. We also no
longer need to hide the custom roles which allows new user default roles to be
displayed without all the crazy logic to decide which mode to show. The old
login-access read only param was removed; This used to map to user-base and we
only displayed it because the role was hidden.
rancher/rancher#23644
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
When a standard user attempted to fresh kubernetes metadata on
the drivers/cluster page it would result in an error notification that
stated 'undefined'. This will allow the backend error message
to surface.
rancher/rancher#25771
-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
This enables '.' to be a valid character in answer varaibles.
So we can support sub.key as a key now.
This also resolves a double render issue that was ran into while
reproducing this issue.
rancher/rancher#23379
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
there is a weird issue in ember engines that resets the route path which can
cause a double render error to be thrown by ember. Easiest fix is to unbind the
param and since this is only dynamic because we're building the list of links
from an array there is no reason for it to be bound.
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
It seems the previous way that the cluster id and project id was fetched from
various addons (alerts and istio) does not work in ember 3.12. After some
investigation it wasn't the corret way to grab those parameters anyway. I've
changed the routes to use the scope service which has the current cluster and
project (if in one) rather than fetch the query params off a parent route
outside the engine.
- 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.
We want to provide a quick way to delete unused cloud credentials.
To do this we're going to show the user the number of node templates
that each cloud credential is associated with.
rancher/rancher#23064
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
The Grafana storage options were confusingly in the middle of the
Prometheus options on the Cluster Monitoring Configuration page.
To resolve this we moved the Grafana options to be below the
Prometheus options and above the advanced otpions.
rancher/rancher#22885
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
When adding the vitual services and destination rules are enabeld we were
showing the import yaml button twice. It needs to be visible on both tabs and we
should be able to pass the or to the rbac check so I removed the duplicates and
moved the button to before the potential other buttons in the istio nav.
rancher/rancher#23155
Westly Wright
Cody Jackson
Westly Wright
loganhz
zhenhua he
wj
n313893254
lvuch
Cody Jackson