- Re-restrict highline dependency. Even though the identified issue was fixed, several tests still fail with the latest highline (1.6.21) that do not fail with highline 1.6.8.
- Remove activesupport dependency. (#21)
- Loosen thor dependency. (#20, @asmega)
- Ensure that long passwords can be properly encrypted. (#19, @gibsop1)
- Ensure compatibility with HighLine 1.6.5. (#16)
- Generalize
datamapper_adapter
andjruby_adapter
transforms to work with any similarly prefixed keys. (#15)
- Add automatic transform for
jruby_adapter
when running under JRuby. (#14)
- Introduce "transforms" -- a way to attach behavior to modify entries on load. See {Bcdatabase.load} for details.
- Add
:datamapper
built-in transform to support sharing one set of entries between ActiveRecord and DataMapper. (#10) - Rework command-line interface for better testability. It's now compatible with MRI 1.9. (#11, #7)
- Provide a better message when working with encrypted passwords and the keyfile is not readable. (#1)
- Improve
bcdatabase encrypt
so that it will work with a wider variety of input passwords and YAML files. The remaining limitations are documented in its online help. (#12) - Interpret empty stanzas as entries made up entirely of defaults. (#13)
- Use
ENV['RAILS_ENV']
instead of the unreliableRAILS_ENV
constant.
- Loosen highline dependency so that bcdatabase can be used in buildr buildfiles.
- Fix command line utilities that were broken in 1.0.3 due to inadequate test coverage. (GH-4)
- Support ActiveSupport 3. ActiveSupport 2 continues to work.
- Tighten up gemspec gem deps. Bcdatabase does not currently work with ActiveSupport 3.
- Update some old syntax for ruby 1.9 compatibility (David Yip)
- Split out from NUBIC internal
bcdatabase
project. (Changelog entries below reflect the relevant changes & version numbers from that project.)
- Fix
bcdatabase encrypt
so that it doesn't re-encrypt already encrypted epassword entries.
- Use the YAML entry name as the "database" value if no other value is provided. This is to DRY up PostgreSQL configurations where the username (already defaulted) and the database name are the same.
- Change default encrypted secret password location
- Support encrypted passwords
- Command-line utility (also called bcdatabase) for creating encrypted passwords
- Gem distribution
Original release.