I have a Django app and am using python-gnupg to encrypt files before storing them on S3.
As part of that, I need to import a GPG public key to do the encryption. In my build.sh, I have a command gpg --import filename.asc.
In the deployment logs, it says something like this:
gpg: key 0A92B0XXXXXXX49B: "Human Name <email@example.com>" not changed gpg: Total number processed: 1 gpg: unchanged: 1
That’s weird, because how could the filesystem already have the key?
Then, after deployment, I log in and do a
gpg --list-keys, and the key isn’t there! In fact, it’s like the
.gnupg directory was never created.
Does anyone have any idea what’s going on? Does the deployment occur in some environment that clears part of the filesystem after deployment?