Skip to content

Conversation

@chewi
Copy link

@chewi chewi commented Dec 19, 2014

  • Don't include MySQL recipes when not using MySQL.
  • Don't include mysql::client at all, database::mysql is sufficient.
  • Do include database::postgresql when using PostgreSQL.
  • Bump database dependency due to breaking changes in mysql-chef_gem.
  • Demote mysql and postgresql cookbooks to "suggests" as they are not strictly required.

@j-miyake
Copy link

+1

@vermut
Copy link

vermut commented Apr 7, 2015

Latest "database" seems to completely break everything. Maybe we should limit it with the 2.3.1?

@chewi
Copy link
Author

chewi commented Apr 7, 2015

Can you elaborate please?

@vermut
Copy link

vermut commented Apr 7, 2015

For example, there is no database::mysql in latest database cookbook

And current zabbix::database directly calls it.

@chewi
Copy link
Author

chewi commented Apr 7, 2015

It was good up until 4.0.2. It has disappeared for a good reason though. The mysql2_chef_gem cookbook should now be used. This change explains the situation quite well.

@vermut
Copy link

vermut commented Apr 7, 2015

I agree completely. But current laradji/zabbix/master is not adapted for a change. That's why I proposed to limit database to 2.3.1 or any latest working version.

Because berkshelf will pull mysql-6.x and database-5.x from current config and it will never work.

 - Don't include MySQL recipes when not using MySQL.
 - Don't include mysql::client at all, database::mysql is sufficient.
 - Do include database::postgresql when using PostgreSQL.
 - Bump database dependency due to breaking changes in mysql-chef_gem.
 - Demote mysql and postgresql cookbooks to "suggests" as they are not
   strictly required.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants