Fixed the issue with log level on the chef config

[ashiqueps]

Description

In the chef config, there are two different options to set the log level. One is the log_level and the other is the verbose. The verbose has more preference, meaning that if it is set, it will overwrite the log_level based on the verbosity level.

Currently, If the verbosity is not set, the code will default the log_level to warn even if the user specifies a different log_level on the config.rb or the credentials file.

This PR will update that flow so that, if the verbosity is not set, it will use whatever value is already set on the log_level and if that is :auto(the default value), it will default to warn.

Related Issue

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.

[johnmccrae]

@nikhil2611 can you take another look at the specs, there are still failures

[johnmccrae]

Can you please check the testers again, there are still failures. Cheers

[sonarcloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

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

See analysis details on SonarCloud