Skip to content
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

Fix resource cloning deprecation for apt-transport-https #351

Open
eyalzek opened this issue May 9, 2017 · 9 comments
Open

Fix resource cloning deprecation for apt-transport-https #351

eyalzek opened this issue May 9, 2017 · 9 comments

Comments

@eyalzek
Copy link
Contributor

eyalzek commented May 9, 2017

Getting the following deprecation message when using the cookbook:

Deprecated features used!
         Cloning resource attributes for apt_package[apt-transport-https] from prior resource
       Previous apt_package[apt-transport-https]: /tmp/kitchen/cache/cookbooks/cassandra-dse/recipes/repositories.rb:31:in `from_file'
       Current  apt_package[apt-transport-https]: /tmp/kitchen/cache/cookbooks/apt/recipes/default.rb:91:in `from_file' at 1 location:
           - /tmp/kitchen/cache/cookbooks/poise/files/halite_gem/poise/helpers/resource_cloning.rb:58:in `emit_cloned_resource_warning'
          See https://docs.chef.io/deprecations_resource_cloning.html for further details.

coming from this line:
https://github.com/michaelklishin/cassandra-chef-cookbook/blob/master/recipes/repositories.rb#L31

is this cookbook actually dependent of apt? most of the apt resources are available as part of the chef core starting version 12.9.1...
https://github.com/michaelklishin/cassandra-chef-cookbook/blob/master/metadata.rb#L12

@michaelklishin
Copy link
Owner

We can't require Chef 12.9.1 just yet.

@eyalzek
Copy link
Contributor Author

eyalzek commented May 9, 2017

What's preventing it atm?

@michaelklishin
Copy link
Owner

@eyalzek there are users who use older versions?

@eyalzek
Copy link
Contributor Author

eyalzek commented May 9, 2017

Yeah but that's not stopping most of the other cookbooks in the chef supermarket to upgrade. This change seems due since chef 13 is already out and will become the standard soon.
If someone wants to continue running an older version they should just use a version tag to apply a constraint and that's it...

@michaelklishin
Copy link
Owner

@eyalzek when "soon" happens, we can move to whatever's available in the core. A deprecation message is not a big deal.

Using older cookbook versions means they won't get any other improvements in master.

@michaelklishin
Copy link
Owner

@eyalzek I think now we can require 12.9 or even 13. Please submit a PR? Note that there are funky things going on with the specs, I'm investigating but not getting very far just yet.

michaelklishin added a commit that referenced this issue Aug 3, 2017
This is to prepare for Chef 13 migration.

References #351.
@eyalzek
Copy link
Contributor Author

eyalzek commented Aug 10, 2017

Sorry, don't have much time for a complete adaptation - also, I'm not entirely sure what are the full changes this requires

@michaelklishin
Copy link
Owner

@eyalzek I did a bit of work on this and getting closer to requiring at least Chef 12.9.1. Unfortunately, some dependency cookbooks used by Test Kitchen and/or ChefSpec seem to need updating for Chef 13. I am not deeply familiar with any of them so it takes time to figure out what part is problematic and whether there were new versions we can use.

But I managed to get things moving towards requiring a recent Chef 12 version.

@michaelklishin
Copy link
Owner

@eyalzek with #365 and a bit of earlier work we are ready to consider more changes, potentially bumping the version to 5.0. Please feel free to send any PRs you had in mind :)

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

No branches or pull requests

2 participants