-
Notifications
You must be signed in to change notification settings - Fork 124
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
Error when converging cookbooks depending on 'aws' cookbook #68
Comments
That gist is missing |
@Jimflip sorry... had left a '/edit' in the link. Corrected now, you should be able to access it |
The
of which AwsEbsVolume is going to have the superclass conflict. Not sure how to work around that. |
Yep, we had a discussion around that on https://gitter.im/chef/chef-provisioning/archives/2015/01/27 and PR #70 has been created to fix this. Another solution is not to use the https://github.com/opscode-cookbooks/aws cookbook. I don't really understand how it is called in the cookbook I am using (https://github.com/bflad/chef-confluence) since, from what I can see, it is only referred to in dependencies with |
I saw in Gitter that you'd asked about how the 'aws' cookbook creates the Chef::Resource::AwsEbsVolume class. That's part of the LWRP magic, e.g. http://www.rubydoc.info/github/opscode/chef/Chef/Resource/LWRPBase, which takes the names you're providing in the LWRP and generates Chef::Resource::CookbooknameResourceName resources. Since the cookbook is 'aws' and the resource is 'ebs_volume' you got AwsEbsVolume from this file: https://github.com/opscode-cookbooks/aws/blob/master/resources/ebs_volume.rb |
Thanks @pburkholder . I ended up working this out but did not have any reference, which you now gave! |
I think we should close this, per the discussion in #70. The AWS cookbook and this have a name collision you shouldn't use both in the same cookbook dependency chain until the functionality of the two are merged. |
I do wonder ... what if we modified the aws cookbook so it used chef-provisioning, and made sure we supported the same attributes? |
Our answer for this at the moment is indeed "at 1.0, you should not use both at the same time." I'd like to see if we can find a way through, so leaving it open at the moment and putting milestone=Later. |
Is any progress being made on this ? I am trying to converge a node that will be the provisioning node running chef-provisioning-aws recipes to create all the other servers in the local infrastructure. I need to use the aws cookbook for the aws_s3_file lwrp to retrieve files from S3 when converging my provisioning server. |
@robcoward The Chef Provisioning team sat down to hash out a pathway forward. #223 is a step toward making this a reality, but it may be a short while before we get there. Perhaps we should close this (per #70 and #223)? The |
Hi @gmiranda23, as a work around for now, I have implemented the aws_s3_file lwrp in my own cookbook to remove the aws cookbook dependency, so I'll be keeping a close eye on #223. |
This is sloppy, this is what's driving people from Chef. You guys maintain BOTH repositories. |
@gmiranda23 @jkeiser any update on this? |
Is there any progress at all on this? over 2 years from the time this issue was noticed... |
Whenever a cookbook using the chef-provisioning-aws driver depends on the 'aws' cookbook, converging fails at cookbooks compilation time with the following error:
Full instructions on https://gist.github.com/esciara/d0921bded64568dc6424
This stops me completly from deploying cookbooks such as https://github.com/bflad/chef-confluence .
The text was updated successfully, but these errors were encountered: