Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do not force profile for AWS session #104

Merged
merged 1 commit into from
Feb 13, 2017

Conversation

wvidana
Copy link
Contributor

@wvidana wvidana commented Feb 5, 2017

  • Let boto3 handle credentials, do not force the use of profile

Tested deploy, tail and delete on a real account (besides the unittest with mocking/placebo)

 * Let boto3 handle credentials, do not force the use of profile
@wvidana
Copy link
Contributor Author

wvidana commented Feb 5, 2017

Fixes #95

@jwilson8767
Copy link

Is it ok to +1 PRs? If so: +1

@josegonzalez josegonzalez merged commit 74cb872 into garnaat:develop Feb 13, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants