Since we allow users to create roles with duplicate
names we're adding the id as a column to allow them
to differentiate between the two.
rancher/rancher#24409
Because the way the apiHost computed property is set we always have protocol in
the field. Added some checks to validate around this side effect.
rancher/rancher#25456
I've overloaded the expand function for shibboleth when using the open ldap
search. Upon open we'll pre-populate with all the data from teh schema, on close
we'll assume the user doesn't want this feature and delete the fields.
rancher/rancher#25459
Adds an empty name to the cluster model creation so it isn't missing if the user
opens yaml editor and knows they should input it
Removes incorrect next usage
Adds logic to handle overriding the name in name-desc when updateYaml is called
Updates form-name-description model observer to watch the two props it actually
cares about
Fixes bug in removeEmpty util which would remove excludedKeys during filter phase
rancher/rancher#24971
There was confusion and misuse around cloudinit and cloudconfig.
This change switches things up so cloudinit is only used for the
legacy creation type and cloudconfig is used for all other creation
types.
Changes the textarea that was used for cloudconfig to
input-yaml to make it clear to users that they can enter yaml.
Switches the vmware cloud credential vcenter input to an input-url
so that we automatically strip the scheme from the input.
rancher/rancher#24314
the old permissions validating was somewhat dumb in its checking, only looking
for local names of roles. This updates the check to loop through all the roles
and fetch there rules upon which we check for the existance of certain rules and
targets.
This also includes fixes for some broken links which happened as apart of the
previous change to this area.
This also fixes a broken translation
rancher/rancher#24341
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
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 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
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
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
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.
- 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 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
When upgrading a multi-cluster-application the template version was set
to the default version instead of the apps current version.
When a current version is present we now use it before using the
default.
rancher/rancher#23101
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
Westly Wright
Cody Jackson
Westly Wright
loganhz
zhenhua he
lvuch
Vincent Fiduccia
n313893254
Tani Fiduccia
phillc
ellisbenjamin