diff options
| author | Vargas, Jorge L <jorge.vargas@thermofisher.com> | 2018-10-27 15:21:18 -0700 |
|---|---|---|
| committer | Marc Cornellà <marc.cornella@live.com> | 2018-10-28 16:01:09 +0100 |
| commit | e4946ef9f94360dd4767c2e58274cd62057822a5 (patch) | |
| tree | c9b8d981c0f323a90c0c84e566e0d3f107b2e73b /themes/macovsky.zsh-theme | |
| parent | f66595ff9e8f4e9ea0f42902fc085823da54e41e (diff) | |
| download | zsh-e4946ef9f94360dd4767c2e58274cd62057822a5.tar.gz zsh-e4946ef9f94360dd4767c2e58274cd62057822a5.tar.bz2 zsh-e4946ef9f94360dd4767c2e58274cd62057822a5.zip | |
aws: change AWS_DEFAULT_PROFILE to AWS_PROFILE
The environment variable name used to be AWS_DEFAULT_PROFILE but the
CLI documentation now only mentions AWS_PROFILE.
https://docs.aws.amazon.com/cli/latest/userguide/cli-environment.html
It seems like the CLI was the only tool using AWS_DEFAULT_PROFILE, and
all the AWS SDKs used AWS_PROFILE, so they standardized on it.
https://onetechnical.wordpress.com/2016/10/07/the-curious-case-of-aws_default_profile/
Note: still left AWS_DEFAULT_PROFILE on the method to set the profile to
maintain backwards compatibility.
Close #7354
Diffstat (limited to 'themes/macovsky.zsh-theme')
0 files changed, 0 insertions, 0 deletions