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
In mobile the user menu was being overlapped by the main content.
To fix this we just needed to update the z-index of the user menu.
rancher/rancher#21914
When editing Azure node templates we failed to
preserve the state of 'Use Private IP To Connect 'when the value of
public ip was 'Static' or 'Dynamic'. We were erroneously overwriting the
value of config.usePrivateIp to false when those public ip values were
chosen.
rancher/rancher#22752
We want to make it more difficult to use unsupported storage providers
to reduce the likelihood of a user accidently using one of these
storage providers.
rancher/rancher#22895
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
* Added select for volume type in node-template
Added standard as volume type for Amazon (ec2 & ebs)
Extracted volume types to amazon.js (used by ec2 & ebs)
In the navigation menu when a user attempted to open a sub-menu the
entire navigation menu instantly closed. To resolve this we now listen
to the router willTransition event to close the navigation rather than
a willRender invocation.
The sub-menu was also overlapping other menu items because it had an
absolute position. To resolve this we now give the sub-menu a static
position.
rancher/rancher#21914
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
Westly Wright
Westly Wright
Vincent Fiduccia
Cody Jackson
loganhz
Sebastiaan van Steenis
n313893254
Meikel Philipp
xiaolu hong