You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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.
The text was updated successfully, but these errors were encountered: