app doesn't have a state so all the logic was a little wonky, the state must
have been removed. setup the app to watch for the deployed condition instead.
refactored the logic about sending out the emit a bit too so that the config
observer sends the event only if the wait for contidion call int he enable has
failed. it seems a little bonkers to wait 60 seconds which can happen some
times. 30 second default should be more than enough in most cases so this really
catches outside cases where clusters may be bogged down and slow.
rancher/dashboard#371 - Scenario 2
We needed a way to support arbitrarily complex parameters in both
type and nesting level. As a temporary solution I enabled the user
to toggle between a key value component and a yaml editor.
To enable this I refactored ResourceYaml into a composable YamlEditor
component that can be used elsewhere.
rancher/dashboard#388rancher/dashboard#380
Add exact to type (link) component
Live data format for events
Pretty cluster providers
Add ago suffix to LiveDate
tweak events headers
remove unneeded suffix
change to unhealthy nodes
only show constraints with violations on overview
ignore tern port files
overview detail gatekeeper disabled bugs
Update percentage bar to take in percentage value
tweak exponents and fix issue wiht max/min
change cluster events default sort
update comments for defaultSortby
cluster infobox feedback
Pass nodes down to InfoBoxCluster to parse only worker nodes info
fix engine config translations
node counts infobox cluster
alignment issues
review feedback
lint warnings