/usr/local/lib/ruby/gems/1.8/gems/chef-0.9.6/lib/chef/rest/auth_credentials.rb:62:in
`load_signing_key’: I cannot read ~/.chef/user.pem, which you told me to
use to sign requests! (Chef::Exceptions::PrivateKeyMissing)
Why does chef-solo require a key to generate a JSON representation of a role
for use with chef-solo?
rake roles calls knife role from file which assumes you want to
upload the role to the server. With chef solo, you are not required to
convert the role to JSON before using it, however--you should be able
to just configure your role_path in solo.rb and run with it. I see
this is not documented on the roles page in the wiki, and the chef
solo page states that you have to convert to JSON first, which is
incorrect. I don't have time to fix these right now, but I'll make a
note to fix them as I'm able. If you're willing to fix them, that
would be greatly appreciated.
Why does chef-solo require a key to generate a JSON representation of a role
for use with chef-solo?
rake roles calls knife role from file which assumes you want to
upload the role to the server. With chef solo, you are not required to
convert the role to JSON before using it, however--you should be able
to just configure your role_path in solo.rb and run with it. I see
this is not documented on the roles page in the wiki, and the chef
solo page states that you have to convert to JSON first, which is
incorrect. I don't have time to fix these right now, but I'll make a
note to fix them as I'm able. If you're willing to fix them, that
would be greatly appreciated.
Dan DeLeo
I'm willing to fix them. Thank you for explaining how to use roles with
chef-solo.
Why does chef-solo require a key to generate a JSON representation of
a role
for use with chef-solo?
rake roles calls knife role from file which assumes you want to
upload the role to the server. With chef solo, you are not required to
convert the role to JSON before using it, however--you should be able
to just configure your role_path in solo.rb and run with it. I see
this is not documented on the roles page in the wiki, and the chef
solo page states that you have to convert to JSON first, which is
incorrect. I don't have time to fix these right now, but I'll make a
note to fix them as I'm able. If you're willing to fix them, that
would be greatly appreciated.
Dan DeLeo
I'm willing to fix them. Thank you for explaining how to use roles with
chef-solo.
I tried role_path and it's still not working. I'll update the wiki once
it works. Here's the code I'm using.
Why does chef-solo require a key to generate a JSON representation of
a role
for use with chef-solo?
rake roles calls knife role from file which assumes you want to
upload the role to the server. With chef solo, you are not required to
convert the role to JSON before using it, however--you should be able
to just configure your role_path in solo.rb and run with it. I see
this is not documented on the roles page in the wiki, and the chef
solo page states that you have to convert to JSON first, which is
incorrect. I don't have time to fix these right now, but I'll make a
note to fix them as I'm able. If you're willing to fix them, that
would be greatly appreciated.
Dan DeLeo
I'm willing to fix them. Thank you for explaining how to use roles with
chef-solo.
I tried role_path and it's still not working. I'll update the wiki once it
works. Here's the code I'm using.
What error are you getting? Chef::Exceptions::RoleNotFound?
Unfortunately, there's not a lot of debug info to be had here, but if
you're willing to hack some into the code, here's where you'd do it:
Why does chef-solo require a key to generate a JSON representation of
a role
for use with chef-solo?
rake roles calls knife role from file which assumes you want to
upload the role to the server. With chef solo, you are not required to
convert the role to JSON before using it, however--you should be able
to just configure your role_path in solo.rb and run with it. I see
this is not documented on the roles page in the wiki, and the chef
solo page states that you have to convert to JSON first, which is
incorrect. I don't have time to fix these right now, but I'll make a
note to fix them as I'm able. If you're willing to fix them, that
would be greatly appreciated.
Dan DeLeo
I'm willing to fix them. Thank you for explaining how to use roles with
chef-solo.
I tried role_path and it's still not working. I'll update the wiki once it
works. Here's the code I'm using.
There is no error. The cookbooks just never run. I'm using the exact
same files on the Opscode platform without issue. Is setting node_name
the proper way to tell chef-solo which role to apply?
Why does chef-solo require a key to generate a JSON representation of
a role
for use with chef-solo?
rake roles calls knife role from file which assumes you want to
upload the role to the server. With chef solo, you are not required to
convert the role to JSON before using it, however--you should be able
to just configure your role_path in solo.rb and run with it. I see
this is not documented on the roles page in the wiki, and the chef
solo page states that you have to convert to JSON first, which is
incorrect. I don't have time to fix these right now, but I'll make a
note to fix them as I'm able. If you're willing to fix them, that
would be greatly appreciated.
Dan DeLeo
I'm willing to fix them. Thank you for explaining how to use roles with
chef-solo.
I tried role_path and it's still not working. I'll update the wiki once
it
works. Here's the code I'm using.
What error are you getting? Chef::Exceptions::RoleNotFound?
Unfortunately, there's not a lot of debug info to be had here, but if
you're willing to hack some into the code, here's where you'd do it:
There is no error. The cookbooks just never run. I'm using the exact same
files on the Opscode platform without issue. Is setting node_name the
proper way to tell chef-solo which role to apply?
Why does chef-solo require a key to generate a JSON representation of
a role
for use with chef-solo?
rake roles calls knife role from file which assumes you want to
upload the role to the server. With chef solo, you are not required to
convert the role to JSON before using it, however--you should be able
to just configure your role_path in solo.rb and run with it. I see
this is not documented on the roles page in the wiki, and the chef
solo page states that you have to convert to JSON first, which is
incorrect. I don't have time to fix these right now, but I'll make a
note to fix them as I'm able. If you're willing to fix them, that
would be greatly appreciated.
Dan DeLeo
I'm willing to fix them. Thank you for explaining how to use roles with
chef-solo.
I tried role_path and it's still not working. I'll update the wiki once
it
works. Here's the code I'm using.
What error are you getting? Chef::Exceptions::RoleNotFound?
Unfortunately, there's not a lot of debug info to be had here, but if
you're willing to hack some into the code, here's where you'd do it:
There is no error. The cookbooks just never run. I'm using the exact same
files on the Opscode platform without issue. Is setting node_name the
proper way to tell chef-solo which role to apply?
Why does chef-solo require a key to generate a JSON
representation of
a role
for use with chef-solo?
rake roles calls knife role from file which assumes you want to
upload the role to the server. With chef solo, you are not
required to
convert the role to JSON before using it, however--you should be
able
to just configure your role_path in solo.rb and run with it. I see
this is not documented on the roles page in the wiki, and the chef
solo page states that you have to convert to JSON first, which is
incorrect. I don't have time to fix these right now, but I'll make a
note to fix them as I'm able. If you're willing to fix them, that
would be greatly appreciated.
Dan DeLeo
I'm willing to fix them. Thank you for explaining how to use roles
with
chef-solo.
I tried role_path and it's still not working. I'll update the wiki
once
it
works. Here's the code I'm using.
What error are you getting? Chef::Exceptions::RoleNotFound?
Unfortunately, there's not a lot of debug info to be had here, but if
you're willing to hack some into the code, here's where you'd do it:
There is no error. The cookbooks just never run. I'm using the exact
same
files on the Opscode platform without issue. Is setting node_name the
proper way to tell chef-solo which role to apply?
The CAPTCHA on every edit combined with no preview button made it
difficult to contribute. It would be nice if Knife was able to locally
convert between the Ruby DSL and the JSON syntax.
The CAPTCHA on every edit combined with no preview button made it difficult
to contribute. It would be nice if Knife was able to locally convert
between the Ruby DSL and the JSON syntax.
First of all, thank you. Every tiny bit that we can improve the docs
helps. I don't know what we can do about the CAPTCHAs, but confluence
does have a preview mode:
It took me a long time to find this at first, I hope you guys won't
have to struggle with it now
The CAPTCHA on every edit combined with no preview button made it
difficult
to contribute. It would be nice if Knife was able to locally convert
between the Ruby DSL and the JSON syntax.
First of all, thank you. Every tiny bit that we can improve the docs
helps. I don't know what we can do about the CAPTCHAs, but confluence
does have a preview mode: