An interesting option is
aws_profile. Here’s an example:
development: aws_profile: dev_profile production: aws_profile: prod_profile
This provides a way to tightly bind
AWS_PROFILE. This prevents you from forgetting to switch your
UFO_ENV when switching your
AWS_PROFILE thereby accidentally launching a stack in the wrong environment.
|whatever||development||default since whatever is not found in settings.yml|
The binding is two-way. So:
UFO_ENV=production ufo ship # will deploy to the AWS_PROFILE=prod_profile AWS_PROFILE=prod_profile ufo ship # will deploy to the UFO_ENV=production
This behavior prevents you from switching
AWS_PROFILEs, forgetting to switch
UFO_ENV and then accidentally deploying a production based docker image to development and vice versa because you forgot to also switch
UFO_ENV to its respective environment.
Pro tip: Use the <- and -> arrow keys to move back and forward.