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
The cluster upgrade notification wasn't properly updating when
the user enabled and disabled a revision. It required that the
page was refreshed before display the fresh data.
This resolves this issue by watching more appropriate keys
int he relevant computed properties. The most relevant
being the revision.@each.enabled on the latestRevision property.
rancher/rancher#23126
Putting togeter a POC for component integration tests
This demonstrates how we can write component integration
tests using the form-key-value component.
This is just a proof of concept demonstrating how to do util tests.
-disable-gpu was removed so the tests can run.
-Chrome was removed from launch_in_dev because it caused
so many browsers to open.
when deploying workloads with an Istio sidecar the port maps require a specific
name to be entered by the user, http. I've exposed the name param but do not
autofill the name, this will be a documentation concern.
rancher/rancher#23105
- We will only conditionally render template/revision section on the
monitoring page if the cluster is using a template. This was
crashing the page before.
- We will now make sure there's a string when invoking replace
when generating the template and revision display names.
- We will now respect the enable flag of template revisions
when determining if an upgrade is available.
rancher/rancher#23126
This is just a proof of concept demonstrating how to do util tests.
-disable-gpu was removed so the tests can run.
-Chrome was removed from launch_in_dev because it caused
so many browsers to open.
I commented out the destinationRules and virtualServices tabs from the
istio-project template, changed some verbiage in the remaining nav tabs, and
added to import yaml link to both tabs to make the ux a little less confusing.
In the next release this page will undergo a redesign so I did not remove the
code.
rancher/rancher#23108
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
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
When upgrading an 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 instead of the
default.
rancher/rancher#23051
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
Westly Wright
Westly Wright
loganhz
Cody Jackson
n313893254
xiaolu hong
Vincent Fiduccia