Running chef manually in a opsworks instance

gistfile1.txt

# put the cookbook path in solo.rb file.
echo 'cookbook_path ["/opt/aws/opsworks/current/site-cookbooks"]' > solo.rb

# create json file incase if you want use the attributes from opsworks.
opsworks-agent-cli get_json > attributes.json

#run chef-solo
/opt/aws/opsworks/current/bin/chef-solo -c solo.rb -o cookbook_name::default -j attributes.json

This is excellent. Thank you! Simple, elegant, and works. This frees up so much hassle doing micro code tests.

One note - depending on the use case, people may want to use 'merged-cookbooks' instead of 'site-cookbooks' - which includes the stock opsworks cookbooks merged in with your own?

Thank you so much. Was digging through AWS docs forever until I found this. So much easier to iterate now.

📦

🌮 🥇 🍔

If you use berkshelf use this instead:
echo 'cookbook_path ["/opt/aws/opsworks/current/berkshelf-cookbooks"]' > solo.rb