fix kitchen-tests

[Stromweld]

Description

This allows for easy testing with test-kitchen of latest version of chef-client in current channel

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Chore (non-breaking change that does not add functionality or fix an issue)

Checklist:

• I have read the CONTRIBUTING document.
• I have run the pre-merge tests locally and they pass.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• If Gemfile.lock has changed, I have used --conservative to do it and included the full output in the Description above.
• All new and existing tests passed.
• All commits have been signed-off for the Developer Certificate of Origin.

[Stromweld]

I think this is ready for iteration 1 of the updates. Additional work is noted in comments within code and kitchen.yml workflow builds.

[johnmccrae]

Hi, can you please squash your commits here?

[johnmccrae]

Let's give this a go once the commits are squashed

[Stromweld]

@johnmccrae on the merge button drop down you can also select squash merge that squashes the commits.

[tpowell-progress]

Move the ifconfig logic

[sonarcloud]

Quality Gate passed

Issues
6 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud