Skip to content
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

Support multiple searches #24

Open
leftathome opened this issue Aug 28, 2013 · 4 comments
Open

Support multiple searches #24

leftathome opened this issue Aug 28, 2013 · 4 comments

Comments

@leftathome
Copy link
Contributor

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
Copy link
Contributor

@leftathome care to point out one of these forks?

@leftathome
Copy link
Contributor Author

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
Copy link

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
Copy link

Following - running into this issue as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants