search

oswaldlabs / chef-rundeck

Integrates Chef with RunDeck, we are referring users to https://github.com/atheiman/better-chef-rundeck as this repository is inactive at this time.
Apache License 2.0
97 stars 85 forks source link

Support multiple searches #24

Open leftathome opened 11 years ago

leftathome commented 11 years ago

Currently, chef-rundeck supports connecting to a single Chef endpoint and running a single Chef search against that endpoint.

It would be great if chef-rundeck could handle multiple searches per endpoint. (We'd also like to be able to search against multiple endpoints)

There are forks of chef-rundeck that do this, so perhaps we'll integrate one of them (with the author's permission, of course) into the main codebase.

josephholsten commented 10 years ago

@leftathome care to point out one of these forks?

leftathome commented 10 years ago

Wow, I remember writing that! How time flies. Anyway, we've kind of got this integrated now after a fashion - basically, it's what chef-rundeck.json is for.

Except for the part about talking to multiple Chef endpoints. I think that could still potentially be useful. I'm not going to kill myself over implementing it but if we're going to refactor to use chef-api I would try to write it with this in mind.

vijaykookkal commented 10 years ago

It there a workaround where i can run 2 processes of chef-rundeck in the same node (on different ports) so that i can connect to 2 different Chef Organizations. It does't seem to work now.

jennyfountain commented 9 years ago

Following - running into this issue as well.