- Chef 10
- Centos / Redhat / Fedora
Author:: Jamie Winsor (reset@riotgames.com)
Author:: Jesse Howarth (jhowarth@riotgames.com)
Maintainer:: Josiah Kiehl (jkiehl@riotgames.com)
Copyright 2012-2013, Riot Games
See LICENSE for license details
Migrate a database using a liquibase changelog.
| Action | Description | Default |
|---|---|---|
| run | Run the migrations | Yes |
| force | Force run the migrations |
| Attribute | Description | Type | Default |
|---|---|---|---|
| change_log_file | The liquibase change log file location on disk, relative to the cwd attribute | String | name |
| jar | The location of the liquibase jar to use | String | |
| connection | Database connection information | Hash | |
| classpath | The classpath to use when executing the migrations | String | |
| driver | Database driver | String | com.mysql.jdbc.Driver |
| adapter | Database adapter | Symbol | :mysql |
| contexts | Contexts to run the migrations in | String | live |
| cwd | The directory to run the migrations from | String | |
| change_log_properties | A hash where the keys are property names and the values are property values for substitution into the change log(s) | Hash | {} |
Unless a key named url in the connection hash is present, the JDBC URL is built from the adapter property and the values of host, port, and database in the connection property hash.
If connection_options is not nil, each key pair is added to the end of the JDBC URL like URL parameters.
When url is present in the connection hash, this value is used instead and the value of adapter and all other values of keys in connection are ignored.