-
Notifications
You must be signed in to change notification settings - Fork 9
Boto has built-in support for loading multiple named accounts, use it. #12
Conversation
e31fe4e
to
dc57d6e
Compare
I need to rebase this now. (and I have done) |
577cce2
to
4a14fb5
Compare
profile_name=instance.aws_profile_name | ||
) | ||
return conn | ||
except NoAuthHandlerFound: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rather than printing an error can you add an error class to errors.py and raise that with a message
Otherwise LGTM 👍 What shall we do about get_config? re the change here and in #45 Maybe we should rewrite it as get_aws_config, get_cf_config, get_project_config etc. PR that first, then rebase our branches? What seems like the least pain? |
@ashb Can you update the description to describe the intentions of this PR, what it might affect, and so on? |
print "[ERROR] No AWS credentials" | ||
print "Create an ~/.aws/credentials file by following this layout:\n\n" + \ | ||
" http://boto.readthedocs.org/en/latest/boto_config_tut.html#credentials" | ||
sys.exit(1) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we print errors to STDERR, not STDOUT?
Changes Unknown when pulling 23a9a84 on use-boto-config into * on master*. |
LGTM 👍 |
I haven’t added a specific task for it as we don’t do this very often. For instance `fab —set aws_region=eu-central-1 … cfn_create`
And final rebase so it merges cleanly. |
By passing tags while creating our cloudformation stack we can propagate these tags to our created resources, enabling easy separation of environments for billing purposes (closes #12)
By passing tags while creating our cloudformation stack we can propagate these tags to our created resources, enabling easy separation of environments for billing purposes (closes #12)
By passing tags while creating our cloudformation stack we can propagate these tags to our created resources, enabling easy separation of environments for billing purposes (closes #12)
This closes #1. This has two benefits:
This will cause everyone to fail with 'you don't have credentials' properly - I'll add something to the readme showing the new config format