Extract mysql_setup recipe into a definition
Refactor mysql_setup definition into zabbix_database lwrp that handles
both mysql and rds_mysql

Move most database attributes from node['zabbix']['server'] to
node['zabbix']['database']
Merge branch 'master' into fix_db_credentials_security
Add Berksfile.lock to .gitignore
Rework database installations into zabbix_database LWRP

Isolate Database installation from Server Installation
  Previously the databse recipes were always called by the server_source
  recipe and they were responsible for writing a server config file

NOTE: This should not be the final structure as database credentials are
still persisted back to the chef server with node.set. They will be
viewable on the server.
Minor README fixes
Attributes alignment for readability
Set default provider for resources/database in such a way that we can
name provider files well
LWRP for doing things with the zabbix source package so that we don't
pull it down multiple times on the same box
Removes debugging Chef::Log.warn calls
Remove errant newline
Remove yum::epel from server_source to allow users to manage their own dependencies
Adds Documentation for each Recipe and LWRP
README Formatting

Switch to using hashtags to create headers because LWRP section requires
4 levels of nesting
README Formatting
README Formatting
Fixes failing Travis build by addressing FoodCritic issues
Fix attribute access to Food Critic
Ensure vagrant box has chef 10.24 because why_run requires 10.14 or
above andthe berkshelf vagrant box currently comes with 10.12

Implement why_run style for databse_my_sql provider so that it properly
notifies
Add rubyblock to set updated_by_last_action so that foodcritic shuts up because FC017 doesn't understand why_run