<p>If what you are looking for is a chef cookbook to manage MySQL, I would recommend checking <a href="https://github.com/chef-cookbooks/mysql" rel="nofollow noreferrer">this</a> It is an officially maintained cookbook. Keep in mind that:</p>

<blockquote>
  <p>This cookbook is concerned with the "MySQL Community Server", particularly those shipped with F/OSS Unix and Linux distributions. It does not address forks or value-added repackaged MySQL distributions like MariaDB or Percona.</p>
</blockquote>

<p>I hope this could help.</p>

CC BY-SA 3.0
2017-09-08T23:50:36.083Z
This 'mysql' cookbook doesn't provide functionality of 'database' cookbook.
AlexD
CC BY-SA 3.0
2017-09-08T19:04:33.493Z
2017-09-08T19:04:33.493Z
Ernesto Iser
<p><a href="https://supermarket.chef.io/cookbooks/mariadb" rel="nofollow noreferrer">MariaDB cookbook</a> added support for <code>mariadb_database</code> and <code>mariadb_user</code> resources in the version 1.5.4 released on May 25 2018.</p>

CC BY-SA 4.0
2018-07-09T04:28:34.397Z
2018-07-09T04:28:34.397Z
AlexD
<p>I frequently use chef database cookbook and it is being deprecated doesn't receive any updates. They even disabled issues on the github so it is not possible to check if any issues I encounter have been discussed and possible solutions were proposed. The deprecation notice says that functionality of this cookbook is supposed to be moved to individual database cookbooks but this still isn't implemented, at least for MySQL. Is there any alternatives to this cookbook or I'm just stuck with creating another fork alongside hundreds of others? </p>

CC BY-SA 3.0
2017-05-08T17:54:07.787Z
A better place to discuss it would chef's slack, specially the brigade channel with is an effort to Take over maintenance of old cookbooks (link is in the community tab of https://learn.chef.io
Tensibai
CC BY-SA 3.0
2017-06-29T13:34:01.817Z
I can't comment so... Man i really wish there was an answer. At least one I could read since anything that happened in Slack is lost for the rest of the world defeating the entire purpose of this site :(
NecLimDul
CC BY-SA 3.0
2017-06-29T15:01:32.103Z
@Tensibai I have to disagree, I'm with NecLimDul on this one - slack is ephemeral, those discussions will dissapear after a short while.
Dan Cornilescu
CC BY-SA 3.0
2017-06-29T15:07:12.863Z
@DanCornilescu Slack is all but ephemeral, all messages are archived and publicly searchable... And as any answer to this can change quickly asking again on a chat system is far better than an outdated fixed post no one will maintain.
Tensibai
CC BY-SA 3.0
2017-06-29T15:08:25.573Z
@NecLimDul FYI there's no rule to prevent asking a question already asked on Slack, nothing is lost on slack neither, that's the whole purpose of the move from IRC to slack: https://chefcommunity.slackarchive.io/general/page-100
Tensibai
CC BY-SA 3.0
2017-06-29T18:15:09.567Z
@Tensibai I stand corrected. Thx.
Dan Cornilescu
CC BY-SA 3.0
2017-06-29T21:38:31.443Z
@Dan no worries :) Chef community support team has, for reasons, a certain reluctance about q/a format, and I have to agree as a bunch of my answers about chef on SO are outdated or superseded with a better way now.
Tensibai
CC BY-SA 4.0
2021-02-06T17:49:47.493Z
@Tensibai, your link to slackarchive.io is dead.
AlexD
CC BY-SA 4.0
2021-02-06T20:50:31.090Z
@AlexD 4 years latter that's a bit less true about the ephemeral part, but the communication FAQ is [here now](https://github.com/chef/chef-oss-practices/blob/master/communication/communication-faq.md#communication-faqs)  and the point stand, 80% of my answers around Chef are still valid if you're on a 4 years old version of Chef, not on recent versions, maintaining them with each major (every year) is a nightmare, that was the reason to abandon a wiki based documentation too and show more an more true.
Tensibai
<chef>
chef database cookbook deprecated
AlexD
# chef database cookbook deprecated

(Asked by: username_0 on 2017-05-08)

I frequently use chef database cookbook and it is being deprecated doesn't receive any updates. They even disabled issues on the github so it is not possible to check if any issues I encounter have been discussed and possible solutions were proposed. The deprecation notice says that functionality of this cookbook is supposed to be moved to individual database cookbooks but this still isn't implemented, at least for MySQL. Is there any alternatives to this cookbook or I'm just stuck with creating another fork alongside hundreds of others?

**Tags:** chef

> **Comments:**
> **username_1**: A better place to discuss it would chef's slack, specially the brigade channel with is an effort to Take over maintenance of old cookbooks (link is in the community tab of https://learn.chef.io  
> **username_2**: I can't comment so... Man i really wish there was an answer. At least one I could read since anything that happened in Slack is lost for the rest of the world defeating the entire purpose of this site :(  
> **username_3**: @username_1 I have to disagree, I'm with username_2 on this one - slack is ephemeral, those discussions will dissapear after a short while.  
> **username_1**: @DanCornilescu Slack is all but ephemeral, all messages are archived and publicly searchable... And as any answer to this can change quickly asking again on a chat system is far better than an outdated fixed post no one will maintain.  
> **username_1**: @username_2 FYI there's no rule to prevent asking a question already asked on Slack, nothing is lost on slack neither, that's the whole purpose of the move from IRC to slack: https://chefcommunity.slackarchive.io/general/page-100  
> **username_3**: @username_1 I stand corrected. Thx.  
> **username_1**: @Dan no worries :) Chef community support team has, for reasons, a certain reluctance about q/a format, and I have to agree as a bunch of my answers about chef on SO are outdated or superseded with a better way now.  
> **username_0**: @username_1, your link to slackarchive.io is dead.  
> **username_1**: @username_0 4 years latter that's a bit less true about the ephemeral part, but the communication FAQ is [here now](https://github.com/chef/chef-oss-practices/blob/master/communication/communication-faq.md#communication-faqs)  and the point stand, 80% of my answers around Chef are still valid if you're on a 4 years old version of Chef, not on recent versions, maintaining them with each major (every year) is a nightmare, that was the reason to abandon a wiki based documentation too and show more an more true.  

---

## 2 answers

### Answer by username_4 on 2017-09-08. Score: 2

If what you are looking for is a chef cookbook to manage MySQL, I would recommend checking [this](https://github.com/chef-cookbooks/mysql) It is an officially maintained cookbook. Keep in mind that:

> This cookbook is concerned with the "MySQL Community Server", particularly those shipped with F/OSS Unix and Linux distributions. It does not address forks or value-added repackaged MySQL distributions like MariaDB or Percona.

I hope this could help.

> **Comments:**
> **username_0**: This 'mysql' cookbook doesn't provide functionality of 'database' cookbook.  

---

### Answer by username_0 on 2018-07-09. Score: 0

[MariaDB cookbook](https://supermarket.chef.io/cookbooks/mariadb) added support for `mariadb_database` and `mariadb_user` resources in the version 1.5.4 released on May 25 2018.


---

