{"push_id":805971078,"size":1,"distinct_size":1,"ref":"refs/heads/release-chef-11.10","head":"b4a1e86a37d20b8084b28d5e4f23f838ac651575","before":"e0e8a069daaac85743d4f3bdaf46bf7ad897d2eb","commits":[{"sha":"b4a1e86a37d20b8084b28d5e4f23f838ac651575","author":{"email":"a0bb2989d2f17b99eff44c35b0d7cdfc1a3d55dc@conradchu.com","name":"Conrad Chu"},"message":"include OpsWorks App environment variables in application.yml\n\nEnvironment variables can now be set for an Application in the AWS console. But they're only made available to application worker processes, not to other commands (rake tasks or rails console via remote login), or even to rake tasks that run during setup and configure events.\n\nThe app-level variables are by nature more granular, and can be protected values, restricted via IAM etc, so there are advantages to using them. Bummer that they're not available outside worker processes, but combining with opsworks_custom_env can fix that too.\n\nThis PR merges those app ENV variables with the stack JSON defined variables into application.yml, so they too may be leveraged by figaro via application.yml. You can mix usage of stack (JSON) and app environment variables.\n\nalso, I added a fix for detection of nginx_unicorn stacks (http://docs.aws.amazon.com/opsworks/latest/userguide/attributes-json-opsworks-rails-stack.html)","distinct":true,"url":"https://api.github.com/repos/GracepointMinistries/opsworks-cookbooks/commits/b4a1e86a37d20b8084b28d5e4f23f838ac651575"}]}