The front end wasn't sending answers to the backend when a user set the the
privateRegistries field when using an RKE template which allowed the field to
be overriden. This was happening because we weren't handling the bracket
notation properly.
rancher/rancher#27166
Since the env vars have to be saved on a cluster there is no easy way of dynamically updating the cluster command without trying to split the string and do all kinds of nasty things.
I refactored the logic for when we show the command for both Custom and Import clusters until after the cluster has been saved. This ensures the user is required to save the cluster before fetching the command on an edit action
rancher/rancher#31529
After some discussions we decided to simplify things since all that's actually needed are keyValues.
I made the changes within the existing component instead of switching to keyValue to reduce risk at this stage of the release.
rancher/rancher#31545
Since the reference types can't exist until the cluster is created I added an option to disable all reference types and use it during RKE create
Even though the backend doesn't indicate the variable name is required we're marking it as such because it casues cluster to fail. No validation will be done at this time.
rancher/rancher#31528
- Fixed issues with determining the provider when editing clusters that are still provisioning.
- Fixed empty values causing problems
- Fixed an issue where the default value wasn't getting set properly for configmaps and secrets when selecting the type and nothing else
https://github.com/rancher/rancher/issues/31023#issuecomment-784717552
custom config has a type of `map[json]` and when we process this for the edit yaml view we can goof some of the keys in the arbitrary JSON.
specifically the `Resources` key gets dasherized and lower cased which borks the cluster on save.
rancher/rancher#30555
exposes the kubeApi Secrets config enabled property which allows users to rotate keys
disable rotate action when prop is not set, we are rotating or, the cluster is transitioning
rancher/rancher#30077
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
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
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
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