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 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
Refactor and decouple launch cluster
adds new routes for selecting cluster, selecting cluter template, and launching
cluster
Add first version of cluster template selection logic
WIP - First version of cluter-template resource pages & components
cluster template index
adds cru-cluster-template
save cluster template and cluster template revision
refactor rke cluster driver and add rke cluster driver to clust temp
add cluster template revision page
template revision changes
more questions
refactor cluster networking into component
cluster template questions components
first itteration of working add question
fixups for ct and ctr's
general fixes
quick revision select on new revision page
Move name, expose ctr name, move ctr source
Refactor ct/ctr table to use grouped form
share member added
single template no revisions rows
translations
translation changes
css toggle
css toggle on all elements
inline override
initial apply cluster template
initial show or lock when applying a cluster template
validation bug
first run at windows support overrides
abstract check override with component that yields
add check for override to most sections
bulk remove cluster template revision
more check override
handle errors better for ctrs
translations
bugs
add toggle to azure cloud provider
auth endpoint fix
computed override check and refactor
fixup question override inputs
remove cluster launch route
review fixups
cluster edit
fixup alias properties for overrides
rancher/rancher#16486
default auth endpoint to true for NEW clusters
Add clusterId to token creation
add scope to api keys table
refactor modal-edit-apikey
Westly Wright
Cody Jackson
lvuch