Options for Figaro on Elastic BeanStalk about figaro HOT 2 OPEN

@tomgallagher i certainly wouldn't do 2. I just dealt with a project where all the keys were in the credentials.yml.enc (yes, including dev and test) and a dev's laptop was stolen. even encrypted, the keys were still committed to the repo and had to be changed.

I'm currently working on an s3 approach to getting files on a system for config and I'll let you know how that goes.

from figaro.

@tomgallagher (and those who might find this later) follow up from my previous comment.

we used the aws-s3 sdk and have copies of our files on an s3 bucket. Then, during deploy, our capistrano task pulls down the file to the shared folder from the bucket. The main thing to leverage is SSHKit's file stream for upload, since that is what the s3 object will return. This is one method that works, and not the only way to accomplish this.

# taken from a Capistrano task
s3 = Aws::S3::Resource.new(
       region: fetch(:aws_region),
       credentials: Aws::Credentials.new(
         fetch(:aws_access_key),
         fetch(:aws_secret_key)
       )
     )
obj = s3.bucket(:aws_s3_bucket).object(:s3_file_path)
upload! obj.get.body, :server_file_path

from figaro.