add decrypt table (the reverse of encrypt table) #87
Conversation
|
I took a look at the Travis CI build error, but was not able to figure out why that error occurred. It looks like starting postgresql server for build 528.9 timed out for some reason. https://travis-ci.org/jmazzi/crypt_keeper/jobs/39288632 |
|
@jmazzi, could you please rerun Travis on the pull request, as one build failed when Postgres wouldn't start. We would love to merge this so that we don't need to maintain our fork. |
|
@serixscorpio @dankohn i'm in the midst of a possible big refactor so I"m holding off on merging anything until I can see how it plays out. Sorry for the delay. |
|
any update on this merge? @jmazzi @serixscorpio |
|
@serixscorpio @dankohn @acrogenesis this PR needs a rebase and then I can merge. |
Conflicts: crypt_keeper.gemspec
…nto add-decrypt-table Conflicts: crypt_keeper.gemspec
|
Also, I noticed the crypt_keeper version in various gemfile.lock used by travis ci need to be updated from 0.18.4 to 0.19.0. 7ff84be |
|
@serixscorpio you need to run |
|
I see. Thanks! Appraisal works great! I'm curious, what's the rationale behind keeping the different gemfile.lock in version control? |
|
@serixscorpio oversight :) - opened #97 |
add decrypt table (the reverse of encrypt table)
This is a functionality I found useful. This is used as a reverse step of encrypt_table! in the context of calling in within a migration. The decrypt_table! method allows one to rollback the migration.