this would take some thinking around, as each provider (vsphere, aws, linode) has their own name for machine types which aren't always straightforward on what resources to expect (take linode machine names for example). However we should validate this as part of provisioning.
use case: https://github.com/rancher/rancher/issues/37808
this would take some thinking around, as each provider (vsphere, aws, linode) has their own name for machine types which aren't always straightforward on what resources to expect (take linode machine names for example). However we should validate this as part of provisioning.