Feature: chef-server integration

[cheeseplus]

Description

Combining 2 issues around chef-server integration

Inventory from Chef-Server via Search

• Feature Request: get target nodes from chef-server chef-workstation#179

This is a feature request(todo) and something to think about. Would be great to get a list of target nodes(names to display and IPs for connection with -a ipaddress) from chef-server by using a query, similar to knife ssh QUERY COMMAND (options)

Examples:
chef-run -t 'roles:www AND chef_environment:dev' -a ipaddress package ntp action=install
chef-run -t 'roles:www AND chef_environment:dev' -a ipaddress service httpd action=restart
or
chef-run 'Q@roles:www AND chef_environment:dev' -a ipaddress service httpd action=restart

Execute target nodes against chef-server content

• Feature Request: run against a real chef server chef-workstation#184

It would be awesome to also be able to use against a chef server, i think it would only work against already bootstrapped nodes, unless workstation is modified to also have the ability to bootstrap. I know there is knife ssh but i think chef workstation is a better interface and the idea of a inventory file to come is great for orchestration. we currently do this with ansible as i have found it easier to use than knife ssh for our use case for blue green deployments.

[tyler-ball]

Triaging all existing issues. This one is interesting - we want to support inventories but the source for that is in flux right now.

For the second part of the issue - the effortless pattern moves away from Chef Server as the source of truth for cookbooks and nodes. I don't think we will end up implementing 'get my cookbooks from Chef Server' as an option for the chef-run command. Happy to have discussions around your use case for this if you have any feedback!

[kmf]

Would love to see the outcome of this.