{"push_id":895456447,"size":1,"distinct_size":1,"ref":"refs/heads/jcr-configure-hash-source-target","head":"da8ee00f70d5db40a03da05a36c5eb964a67a0c7","before":"30ffbb9081f446b5f1ac6fe2340934b735f71d7f","commits":[{"sha":"da8ee00f70d5db40a03da05a36c5eb964a67a0c7","author":{"email":"4ce87f5ca5596825d366b739cd5c4750d74e0217@gmail.com","name":"Collin Redding"},"message":"Remove configuring yaml databases\n\nThis removes configuring yaml databases and being able to use a\n\"database name\" in the source and target. This is to simplify\ndumpdb and avoid all the yaml parsing logic. A `database.yml` can\nstill be used with dumpdb it just has to be manually parsed and\nused in the source and target.\n\nThe source and target now always expect a hash of values. This\nworks as it previously did. A `Db` object is built and provided as\nthe source and target in an initialized dumpdb script.\n\nThis also includes a few internal cleanups to the `Db` class and\nupdates its tests to our latest conventions. It now uses symbol\nkeys instead of string keys which is just to match how it hsubs its\nvalues into the cmd templates. The other tests could be updated to\nour latest conventions but we don't want to worry about making\nthose changes right now.","distinct":true,"url":"https://api.github.com/repos/redding/dumpdb/commits/da8ee00f70d5db40a03da05a36c5eb964a67a0c7"}]}