-
-
Notifications
You must be signed in to change notification settings - Fork 376
-
-
Notifications
You must be signed in to change notification settings - Fork 376
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
knife cookbook upload chef-rvm fails #20
Comments
Sorry, you're totally correct. I've updated this attribute value to |
I downloaded the latest version (0.7.0) and experiencing the same problem as @gangster: I'm using Chef 0.10. if it helps. |
Just tracked it down. The README.md appears too long to be included in metadata.rb. I'll push an update to fix. |
Thanks! It worked. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Hi. I am very new (~1 day) to Chef so this in fact may not be a bug and may be user error. With that said, when I try to upload the Cookbook up to opscode, I get the following error
$ knife cookbook upload chef-rvm
ERROR: Chef::Exceptions::ValidationFailed: Option type must be equal to one of: string, array, hash, symbol! You passed "boolean".
It would appear the offending code is in metadata.rb:
attribute "rvm/install_rubies",
:display_name => "Can enable or disable installation of a default ruby and additional rubies set attribute metadata.",
:description => "Can enable or disable installation of a default ruby and additional rubies set attribute metadata. The primary use case for this attribute is when you don't want any rubies installed (but you want RVM installed).",
:type => "boolean",
:default => true
Any ideas on how to get around it? I tried changing :type to "string" and :default to "true" but for my troubles all I got was:
Uploading chef-rvm [0.6.0]
ERROR: EOFError: end of file reached
The text was updated successfully, but these errors were encountered: