Open mcgarrah opened 7 years ago
Setting the AWS_DEFAULT_PROFILE
environmental variable seems to be a work around for passing the --profile
. This gets me around the issue.
I'm having a phenomenal time working on this. A Serverless CMS is a awesome idea and looking forward to doing more work on it.
Thanks for the great product.
Hi @mcgarrah,
Glad to hear you are enjoying the tool. This project was a final year Computer Science project for the team and I, and is no longer under development as we have all graduated and moved onto other ventures. It was an enjoyable experience, with plenty of challenges faced and new skills obtained.
Cheers, Adam
I'm setting up my first deployment and have historically used profiles for the multiple AWS account.
$ aws configurate aws-test1-account --profile aws-test1
Access Key: asdfasdf Secret Key: secretasdfsecretasdf Region: us-east-1 Format: NoneThis lets me jump between accounts. I do not set a [default] profile in my credentials file. The command for setting up the CMS initially does not seem to allow for the --profile option. I'm reading the code now to see if I can find a place to insert it.
This is the command that I expected to be able to add a --profile.
$ python setup.py test1-cms us-east-1
I'm looking in the cms_functions.py and the
class AwsFunc:
comment about awscli configuration which is what I've done above or an aws configuration file which read up on from:http://docs.aws.amazon.com/cli/latest/userguide/cli-environment.html
This points to a ENV Variable:
AWS_DEFAULT_PROFILE
which might suit my purposes for a temporary change to the default profile.Do you have any suggestions on a better solution?