Skip to content

unique names for ohia resource #204

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

unique names for ohia resource #204

wants to merge 1 commit into from

Conversation

coreyappleby
Copy link

Chef 13 doesn't allow resource cloning, so the ohai "reload" resource needs unique names for client and server.

@coreyappleby
Copy link
Author

Previous ohai[reload]: /tmp/kitchen/cache/cookbooks/ssh-hardening/recipes/server.rb:43:in from_file'
Current ohai[reload]: /tmp/kitchen/cache/cookbooks/ssh-hardening/recipes/client.rb:23:in from_file' (CHEF-3694)/tmp/kitchen/cache/cookbooks/poise/files/halite_gem/poise/helpers/resource_cloning.rb:58:in emit_cloned_resource_warning'.
Please see https://docs.chef.io/deprecations_resource_cloning.html for further details and information on how to correct this problem. at /opt/chef/embedded/lib/ruby/gems/2.3.0/gems/chef-12.22.5/lib/chef/formatters/doc.rb:419:in deprecation'

@coveralls
Copy link

Coverage Status

Coverage remained the same at 99.825% when pulling d81caba on coreyappleby:chef13 into f042bc0 on dev-sec:master.

@artem-sidorenko
Copy link
Member

@coreyappleby many thanks for this PR! However, this was already resolved with #203 :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants