{"push_id":1168358508,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"d84315c29bbe45ab979a94f0bcecfcb7ecb307a8","before":"09fd5a4ac2aa734452c8582d7f8a77401a8118c7","commits":[{"sha":"c457767edec96a2e24eefa3ef574da15d329231b","author":{"name":"David Goodlad","email":"d8099b0f90e53c29d29eb12a7a3caa5af4f12681@goodlad.net"},"message":"Don't kill AWS_CONFIG_FILE in forked environment\n\nThe aws CLI needs access to the config file for more than credentials,\ne.g. setting the default region, or enabling the cloudfront cli preview\nfeature.\n\nThis variable was originally nuked in cb5710d. According to @lox's\nmemory:\n\n> I seem to recall the issue is that subshells would try and read the\n> aws config file, rather than use the injected credentials and this\n> lead to strange combinations of credentials and failures.\n\nWhile this could cause trouble, it's probably a misconfiguration to have\ncredentials in your config file for profiles managed by aws-vault.\n\nFixes #65","distinct":true,"url":"https://api.github.com/repos/99designs/aws-vault/commits/c457767edec96a2e24eefa3ef574da15d329231b"},{"sha":"d84315c29bbe45ab979a94f0bcecfcb7ecb307a8","author":{"name":"Lachlan Donald","email":"842d5b29cccdef0be6ca815130d6952ea99f7410@ljd.cc"},"message":"Merge pull request #68 from dgoodlad/keep-aws-config-file-env-var\n\nDon't kill AWS_CONFIG_FILE in forked environment","distinct":true,"url":"https://api.github.com/repos/99designs/aws-vault/commits/d84315c29bbe45ab979a94f0bcecfcb7ecb307a8"}]}
{"actor":{"display_login":"lox"}}