As AWS_ACCESS_KEY_IDs should be unique the awsenv can determine which env is currently active (as long as the lockagent is running) and display the env to be used in the shell prompt. This would ensure the user knows about which env is currently active and does not execute stuff in the wrong env.
Luzifer
commented
9 years ago
As AWS_ACCESS_KEY_IDs should be unique the awsenv can determine which env is currently active (as long as the lockagent is running) and display the env to be used in the shell prompt. This would ensure the user knows about which env is currently active and does not execute stuff in the wrong env.