You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Before we introduced node['virtualization']['systems'] we used node['virtualization']['system'] and node['virtualization']['role']. This only allowed for a single virtualization, but we detected multiple technologies so the last writer won. We introduced the systems array in Chef 11 (pretty sure) which provides a much more reliable way to detect virtualization systems. We should create a Foodcritic rule and move people to the new system so we can fully deprecate the less than ideal older interface.
Scenario where the old interfaces fail:
virtualization
systems
kvm: host
vmware: host
system: vmware
role: guest
The text was updated successfully, but these errors were encountered:
tas50
changed the title
Chef 15: Remove legacy data in the Virtualization plugin
Chef 16: Remove legacy data in the Virtualization plugin
Nov 23, 2018
There is not. We probably need to have a rule in place for a while before we can consider removing anything.
tas50
changed the title
Chef 16: Remove legacy data in the Virtualization plugin
Future Ohai: Remove legacy data in the Virtualization plugin
Mar 30, 2020
Before we introduced node['virtualization']['systems'] we used node['virtualization']['system'] and node['virtualization']['role']. This only allowed for a single virtualization, but we detected multiple technologies so the last writer won. We introduced the systems array in Chef 11 (pretty sure) which provides a much more reliable way to detect virtualization systems. We should create a Foodcritic rule and move people to the new system so we can fully deprecate the less than ideal older interface.
Scenario where the old interfaces fail:
The text was updated successfully, but these errors were encountered: