base barclamp framework
cmdb->chef
Fix crowbar.yml to make sure it is installed after the Crowbar barclamp.
Move the bc templates into the right directory.
Fix default templates so that they provide useful information and so that they validate.
Merge pull request #1 from VictorLowther/pull-req-master-c13c7bc6595ddc4546dce7433a9ddf98647ff6c2

Make chef barclamp not break installation. [1/1]
add creating a base cmdb instance to the import of chef
names can't have -, silent faliure in migrations
Merge pull request #3 from aabes/pull-req-master-22dafe8f1da6002e31b5ba3027568a4476fd5495

CMDB/proposal code and tests. WIP [2/2]
fix model dir name
Merge pull request #4 from aabes/pull-req-master-2e40d582592a6fafb43be07393f0a2ec76adf4ef

fix model/models [1/1]
move chef things to chef bc
A bunch of changes:
 * move cmdb_chef from crowbar to the chef barclamp
 * add cmdb chef connection info
 * fix issues around saving events and runs (must specify type explicitly)
 * start on a more content-full proposal - server & connection information
 * add chef to the crowbar cli, that replaces the client_key from the proposal with the actual key infromation.
Merge pull request #5 from aabes/pull-req-master-33d5ba0a8e9efe8a6125d594de548d6c58812b59

CDMB progress - cmdb_chef to chef barclamp, cmdb test fixes [2/2]
fix column name for relationship between chef_cmdb and conn_info
add description & order for servers in the proposal
more progress towards talking to an off server chef server
1) cmdb chef & conn info created in the db when proposal committed
2) start working on (WIP) attempts to monkeypatch the REST chef api to feed it the key from the db.
chef makes it hard... each access path (query, node and databag) seems to be doing something slightly different w/ regards to the way they interact with the REST api client)
fix typo
better monkeypatch for REST, replace the authenticator for all cases, as long as we've been initialized
preliminary docs