Existing key on S3 gets overwritten

[scookdev]

When running nib-crypt init for the first time when initializing an application, a new key gets created and uploaded to S3, overwriting the existing key, rather than pulling it down. When this happens, decrypting the secrets file will fail.

[mgeitz]

Want to add to this issue; the key pushed this morning at 11:24AM was the first key ever pushed for incent-config-gem repo which already had an encrypted secrets file committed to it.

[scookdev]

This scenario is currently being handled: https://github.com/technekes/nib-crypt/blob/master/lib/nib/crypt/initializer.rb#L12

Can we surmise that the secrets file was encrypted with a key that was not uploaded?