Update WARN message in 9.x for array of hashes in policy reference to ERROR

[scottvidmar]

Cookbook version

9.x.x

Chef-client version

any version will show this.

Platform Details

All platforms are impacted.

Scenario:

When using old syntax for profile references, arrays of hashes issues a WARN log message for a fatal error. Can we please update that to ERROR message?

Steps to Reproduce:

Use an array of hashes for profile references in the attributes file.

Expected Result:

An error message is thrown into logs to draw immediate attention to the reason profiles aren't able to be pulled down.

Actual Result:

Shows up as a WARN message.

Code here: https://github.com/chef-cookbooks/audit/blob/aafd15dbc13b766497aded4988eff01486c288ec/files/default/handler/audit_report.rb#L44

Impact:

Warn is typically used to just show oddities in an application. By making this a WARN in cookbooks that will not function in this scenario, we aren't being clear that this is something that is fatal to the cookbooks ability to function, but not the service (chef) overall.

[welcomebot]

Hey There
It looks like this is the first issue you've filed against the chef-cookbooks project. I'm here to offer you a bit of extra help to make sure we can quickly get back to you.
Make sure you've filled out all the fields in our issue template. Make sure you've provided us with the version of chef-client you're running, your operating system and the version of the cookbook. If you're not using the most up to date version of the cookbook then please make sure to update first. Lots of things change between versions even if you're issue isn't listed in the changelog. Finally please give us a detailed description of the issue you're having. The more we know about what you're trying to do, what actually happens, and how you can reproduce the problem, the better.

If you're looking for more immediate troubleshooting help make sure to check out #general on the Chef Community Slack. There's plenty of folks there willing to lend a helping hand. Thanks for the first issue. We hope we can get back to you soon with a solution.