-
-
Notifications
You must be signed in to change notification settings - Fork 30
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
Assume a default query key when none provided in knife zero chef_client QUERY
#33
Comments
hmm... https://docs.chef.io/knife_ssh.html If I implement specific usage to knife-zero, then it's getting harder to follow chef-core updates ( and the edge of chef often cases regression ...). But, I seem to better way to use name or fqdn by default. In that case, there is a need to be careful not to use as a regular expression. |
You're right about it diverging from chef-core. Perhaps it would be welcome there. Created a ticket here for discussion: chef/chef#3526 |
Thank you for create issue to core 😃 |
bwaha. the label. |
fyi this would work for |
@patcon great! I've add below to Gemfile and tested it.
There are node which is named knife-zero02. It have IP
In this case, I should pass an ipaddress to fuzzy_query.
How about include name to fuzzy target?
|
I'm down, but it sounds like Lamont thinks this logic should match the search logic, so maybe mention the idea in the chef issue? Also, I'll make sure to leave it around this time, but I'd recommend against using my feature branches on your master, as my habit is to delete them after merge, and sometimes they break :) |
It seems that even when there's a
node/example.com.json
,knife zero chef_client example.com
doesn't work, and instead, we must useknife zero chef_client name:example.com
Would be great if
knife-zero
assumed a default key, eithername
orfqdn
(I prefer "name", as it should intuitiveless always match the json filename innodes/
. Yes, in the current knife-zero this is also the fqdn, but this need not necessarily be the case in the future)The text was updated successfully, but these errors were encountered: