for this field anything other than 'standard' is the same as 'basic'
update the ui default to basic, the UI should always send a value not empty string but for clusters created outside the ui we will display basic if not standard
rancher/rancher#29908
default on the backend was change from `standard` to `""` to alievate issues with upgrading clusters that didn't have a lb sku before
rancher/rancher#29908
Rather than add a warning the user needs to exit I've added a send to the socket for `exit\r\n` to disconnect the process before the socket closes
rancher/rancher#16192
For imported or custom clusters that never had a host register there was
never a way to get back to the registration command. This exposes a new
modal and button ont he cluster dashboard the allows the user to fetch
this command if the cluster doesn't have any nodes.
rancher/rancher#28548
Add import-command component the import command on imported clusters
this is the first step to exposing the command as an action in the modal for show command
Create CustomCommand component for modal show command
add custom input to show command modal
translations
this issue cropped up after a large dependency upgrade and I believe it has to do with some underlying ember changes. Basically we'd hit a race condition where we'd click next before the observer has had a chance to update the project id.
Found an additional issue where the observer on zone change would cause all the fetchs to fire again after the cluster has saved because we merge the results, I added checks to see if we'd saved as saving was already set false but we hadn't started destroying yet.
rancher/rancher#29646
when i ugpraded ember basic dropdown the mechanism we previously used to close the dropdown on click was removed and as a result I added the recommended method closing the dropdown.
the problem was that page-header-project and hover-drowndown worktogether to close the dropdown as well and the conflict was causing a full page refresh due to the close method.
ive dropped the conflicting action and instead moved the close logic to hover dropdown in the routeWillChange method since its knows its context in regards to the dropdown.
at this point the `a` in page header project will have been magically clicked and the component is done with publicDropDownApi so it can be set null.
There are changes required for the ember upgrade but additional changes
for individual libs are also present. Commit has been squashed, see
individual commits if needed.
There are a bunch of HBS changes as well. These are to deal with a
couple new rules and there impact is low. The button one has bitten us a
few time so this seemed great to add IMO.
update ember 3.12.4
ember 3.13
fixes for new eslint rules
ember 3.13->3.14
ember3.14->3.16
ember3.16->3.20
3.20 lint rules
yarn upgrade
update ember-optional-feature
update deps that can go to patch versions
upgrade major versions that are possible
update ansi_up
only reset term var if we're not destroying
prevents new ember 'same computation' error
update async
upgrade dot-object
new-catalog - add set to deal with new warning
marked-down - drop call into next to ensure its called at the correct time
upgrade ember-assign
update ember-cli-clipboard
remove unused & deprecated ember-cli-release
remove unused drag-drop lib
use set on tracked prop
update ember-flatpickr && cli-test-loader
upgrade ember-href-to
update filesaver
update liquid-fire and ipaddr
upgrade jsondiffpatch
upgrade marked
upgrade semver
update xterm
Update ember-basic-dropdown
the library has changed quite a bit and no longer provides an addon for the content-item where we handling the click event to close the dropdown,
thus click events must be added manually to the items being clicked to close the dropdown.
udpate dompurify
fix page header project styles
Bump ember api store, remove npm-run-all
Autofix button types from hbs linting
this change looks large but only adds `type` button to any buttons that dont have a type, which should help to reduce weird side effects
more hbs lint changes for no-negate-condition
turned off a couple rules that could be too much to test right now
Cluster version can only deviate from node group versions by 1, so if any node group version is more than 1 behind the cluster can not upgrade until the node groups upgrade
New node groups should version set to that of the cluster not the other node groups
rancher/rancher#28968rancher/rancher#29166
This makes the node group upgrade ux closer to the ux of AWS console.
Removes the node group version select, replaces with a radio.
Adds logic to set the new nodegroup version on edit to the version of other nodegroups
Adds logic to prevent node group version upgrade when cluster version is being upgraded.
rancher/rancher#28965rancher/rancher#28966rancher/rancher#28968
- The entire tag collection needs to be sent if it changed
- I noticed that when editing a tag key each letter was added so I resolved that as well
rancher/rancher#28949
adds both tooltip warning on cluster row and alert warning on cluster dashboard
version can only be updated on edit when cluster version is different from node group version
all other times we set the node group version to the clusters version
rancher/rancher#28335
Pod scale minimum was incorrectly set to 1. This sets the default back
to 0. Adds a nullible flag to input-int as this is allowed in most cases
where we are using the component. Defaults to false.
Formatting fixes
rancher/rancher#28168
Turns out that the min value that the backend accepts won't allow
upgrades to complete. This switches the value to the default value to
mitigate that issue.
rancher/rancher#27333
error handler
wip - dev for aws cloud creds
wip - refactor aws login
wip - kms key
wip - encrypt secrets
wip - private access & vpcs
wip - translations and formatting
wip - more cleanup
remove unneeded code
wip - node groups
add ability to disable value label
fix double import, fix double negative disable add button and expose
addbuttonenabled
clean up public access and node groups
cleanup variable names and default config
eks regions
wip - eks v2 select
differentiate v1/2 amazon eks providers
clean up node groups, translations
unionize top errors
Consolidate aws util statics
WIP - Import/Cloud Creds
tweak cloud cred events for eks driver
WIP new import selector
drop unneeded variables eks import
kms keys cleanup
allow user to enter if the kms keys call fails
firefox styles
drop vpc selection and group subnets by vpcs
import cluster name input if allClusters fails to load from eks
make eks import a bit more dynamic
fix bug in driver eks for default subnet
more imported cleanup
eks v2 edit
eks v2 vendors
remove use cloud creds temp branchs
push current version to version choices if it doesnt exist
eks v2 rename cloudcred param
fix eks v2 versions
clean up for pr
When upgrading rancher the old 1.4 cis profiles were removed which prevented
the currently selected profile for scheduled scans to be selected.
This adds a selected profile to the options if it's not present allowing the
profile to be selected by default. If a different profile is selected and saved
the option will no longer be present. This option will also not be present in
the manual run scan modal.
rancher/rancher#27867rancher/rancher#27866rancher/rancher#27374
The parameters are shown with the known keys but it's
no longer limited to only the known keys. New keys can
be added and they will be sent to the backend as long as
they have values.
rancher/rancher#27220
jesse.millan
Westly Wright
Westly Wright
Cody Jackson
Denise
Matt Nikkel
jrosinsk
Vincent Fiduccia
loganhz
Bastian Hofmann