Downgrade mysql cookbook for now
It doesn't play well with our current dev server setup
This commit is contained in:
@@ -1,22 +1,5 @@
|
||||
# mysql2_chef_gem CHANGELOG
|
||||
|
||||
## 2.0.1 (2017-03-28)
|
||||
|
||||
- Include usage examples for installing on a mariadb server and included a note in the readme regarding the 2.0 changes.
|
||||
|
||||
## 2.0.0 (2017-03-28)
|
||||
|
||||
- Converted the previously HWRP resources/providers to a custom resource. This changes the behavior of choosing to install on mysql or mariadb in a breaking way. Instead of specifying the providers you need to call the resources directly. Specifying mysql2_chef_gem will default to mysql, but using mariadb will require using the mysql2_chef_gem_mariadb resource directly.
|
||||
- Increase the minimum chef version to 12.5
|
||||
- Require mysql cookbook 8.2+ and build-essential cookbook 2.4+
|
||||
- Install the 0.4.5 gem by default
|
||||
- Expand test recipe to cover more scenarios
|
||||
- Switched testing to use Delivery local mode
|
||||
- Switched from kitchen-docker to kitchen-dokken and removed testing for CentOS 5 / Ubuntu 12.04 as these are both going EOL
|
||||
- Switched from Rubocop to cookstyle for linting
|
||||
- Removed yum/apt from the Berksfile
|
||||
- Remove test dependencies from the Gemfile and instead use ChefDK for testing
|
||||
|
||||
## 1.1.0 (2016-04-27)
|
||||
|
||||
- Added a chefignore file
|
||||
|
||||
Reference in New Issue
Block a user