The tags and custom attribute requests were never being made due to a recent change.
This change filtered out requests that didn't have a datacenter degined for everything but the datacenter resource. However this should've included 3 other resources that don't need a datacenter during the request.
rancher/rancher#31285
* Cloud credentials support for phoenixNAP driver.
* space added
* code formatting
* init function removed, name param removed from the arrays that populate
dropdowns
Co-authored-by: pavlej <pavlej@NSDT-PAVLEJ.ccbill-hq.local>
For props that have options that depend on credentials or datacenter this ensures that the props are reinitialized to one of the options.
rancher/rancher#30074
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
I noticed fields wouldn't update if the credentials changed
if the datacenter value stayed the same. This ensures that
all of the other values will recompute by forcing the datacenter
value to change.
rancher/rancher#26997
Making the clearing on save more comprehensive. Now clear the
following fields when appropriate:
- cloneFrom
- boot2dockerUrl
- contentLibrary
rancher/rancher#24747
There was confusion and misuse around cloudinit and cloudconfig.
This change switches things up so cloudinit is only used for the
legacy creation type and cloudconfig is used for all other creation
types.
Changes the textarea that was used for cloudconfig to
input-yaml to make it clear to users that they can enter yaml.
Switches the vmware cloud credential vcenter input to an input-url
so that we automatically strip the scheme from the input.
rancher/rancher#24314
The backend was setting the default to legacy so that the legacy
template would still work when users migrate to the latest
version of the driver. This was causing the default value to
be legacy when creating a new vsphere template. Forcing
the backend to change the default will likely lead to problems
with the migration so we're making the change on the front end.
Ultimately we use the existing set default logic if a vsphere template
is being created (as opposed to edited) instead of just when the
creation type doesn't exist or is invalid.
We also changed the text for the legacy value to be friendlier.
rancher/rancher#24060
When using an older vsphere node template in the latest version it was
possible that a user entered value would not be a valid option. When
the value isn't a valid option the dropdown has nothing selected. To
improve the UX we now notify the user that the current value is no
longer valid and sask them to select a new value.
rancher/rancher#23920
The backend has made a new implementation of creationType which allowed
me to remove the creationMethod concept and just use creationType.
This change allows us to properly populate the creation type form fields
when a user edits a vsphere nodetemplate.
rancher/rancher#23812
The keys for custom attributes needed to be unique. To enforce the
unique constraint I created the FormContextualKeyValue component.
This component behaves similarly to the FormContextualSelectArray
but handles key value pairs.
rancher/rancher#23782
When editing a vsphere node template that used a RancherOS ISO
creation method it crashed the page due to an array not existing.
I also noticed that the tags, custom attributes and networks weren't
loading when editing so I resolved those issues too.
rancher/rancher#23796
We want to provide the owner as additional information when showing
node templates on the node templates page. We also want to make it so
that when selecting a node template the users templates will be grouped
and sorted to the top by default.
rancher/rancher#23325
Vincent Fiduccia
wujun
Lauren Harden
jesse.millan
Westly Wright
pavlej
Neil MacDougall
Cody Jackson
pajuga
Luther Monson
Westly Wright
GGGitBoy