ineednewpajamas

Issue persists in chef-server-core-15.0.9 but with updated versions ``` /opt/opscode/embedded/lib/ruby/gems/2.7.0/gems/chef-vault-4.1.10/lib/chef-vault/version.rb:18: warning: already initialized constant ChefVault::VERSION /opt/opscode/embedded/lib/ruby/gems/2.7.0/gems/chef-vault-4.1.5/lib/chef-vault/version.rb:18: warning: previous definition of VERSION was here /opt/opscode/embedded/lib/ruby/gems/2.7.0/gems/chef-vault-4.1.10/lib/chef-vault/version.rb:19: warning: already initialized constant ChefVault::MAJOR /opt/opscode/embedded/lib/ruby/gems/2.7.0/gems/chef-vault-4.1.5/lib/chef-vault/version.rb:19:...

The current behavior seems at odds with this line in the docs "Once turned on, the Compliance Phase always outputs its results in the CLI on manual runs. The output...

Looks good using develop5. Thank you.

Note that this cookbook also relies on hostsfile and that also has the issue and doesn't seem to be maintained: https://github.com/customink-webops/hostsfile/issues/102