{"push_id":895461003,"size":1,"distinct_size":1,"ref":"refs/heads/jcr-configure-hash-source-target","head":"f5bafbdc0d3761c10dd92fd6d08b5dbe2f486af8","before":"da8ee00f70d5db40a03da05a36c5eb964a67a0c7","commits":[{"sha":"f5bafbdc0d3761c10dd92fd6d08b5dbe2f486af8","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\nAdditionally, the source and target can now be configured with a\nport. This previously wasn't an option but it now is.\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. It also no longer supports the\naliases for its values that it previously did. The other tests\ncould be updated to our latest conventions but we don't want to\nworry about making those changes right now.","distinct":true,"url":"https://api.github.com/repos/redding/dumpdb/commits/f5bafbdc0d3761c10dd92fd6d08b5dbe2f486af8"}]}