-
Notifications
You must be signed in to change notification settings - Fork 103
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 launch should create a chef node if not present #62
Comments
I think there were unresolved permissions issues which prevented this, the last time it was tried by Chris. |
Ah, right. The client that creates the node is the one that then owns it. It would probably be best if knife force-created the client and the node Now I remember why this wasn't simple. On Tue, Oct 25, 2011 at 2:17 PM, Nathaniel Eliot <
|
Well, if it were simple, we'd have done it already . . . I agree that bootstrapping in the pre-made client definition seems more correct than relying on the client to make client and node itself. |
this might work:
If so, Bob's our uncle. flip On Tue, Oct 25, 2011 at 2:36 PM, Nathaniel Eliot <
infochimps.com - discover data |
Fixed. If the client doesn't exist, knife creates it and saves the client key. If the node doesn't exist, and you don't have the client key, knife will error out. You have to delete the client, or create the node yourself and then adjust permissions. |
+1 |
Knife should create the chef node if it's missing.
This causes problems with sync and lots besides when it doesn't
flip
The text was updated successfully, but these errors were encountered: