knife autocompletion issue and cache issue

[clarkewd]

two issues with your version:

1. autocompleting early on in the sentence, i.e. knife node should have a default list of options built in and should not need to perform an expensive command query. in less words - why is it this slow?

2. for things that do need to make a query, i.e. knife node list you should probably implement some caching because the performance is pretty slow. there was at least some attempt at caching in the original version even though the environment autocompletion did not work well

[clarkewd]

Hmm, maybe I was fooled into thinking I was looking at the "original" version I had saw a while back. Check out this version - older but I think it works better. Can you improve from that one? :)

[vindimy]

Hey there,

Thanks for your feedback. The delay seems to come entirely from "knife" command calls. I timed how long it takes for something like "knife node --help" to return and it's about 2 seconds (which is ridiculous since it's not actually doing anything). So while hard-coding values into autocomplete script would work around the issue, I'll contact Chef mailing list instead and ask why "knife --help" commands are taking so long to return.

[clarkewd]

cool - thanks. it may also be worth looking into the code for that command. i also submitted a pull request for the other link i shared which fixes the "knife environment" issue due to a typo so the original script is working pretty good for me now