Open ianwestcott opened 9 years ago
I'd actually like this test for those arguments to be dropped entirely. Making these arguments/ENV required makes route53-transfer break when credentials have already been configured in some other way. Boto supports IAM Roles, site wide /etc/boto.cfg
config, ~/.aws/credentials
shared between SDKs, and its own ~/.boto config file.
If credentials are already configured in any of these places. route53-transfer won't use them.
If I run
route53-transfer
without passing--access-key-id
and--secret-key
, and without settingAWS_ACCESS_KEY_ID
andAWS_SECRET_ACCESS_KEY
in my environment, the error I get looks like an error from AWS:It would be more clear to the user if the script validated the existence of the AWS credentials and gave a more explicit error if they were not set by either means.