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

Add support for --profile flag for specifying AWS credentials profile #29

Open
frewsxcv opened this issue Feb 27, 2017 · 3 comments
Open

Comments

@frewsxcv
Copy link

Instead of relying on environment variables or the "default" profile for AWS credentials, it'd be great if one could specify --profile for cfn-flow networking fetching commands (deploy, list, etc.) that specified which AWS credentials profile to use.

This matches the CLI interface that the official AWS CLI tool provides:

http://docs.aws.amazon.com/cli/latest/reference/

@jamesla
Copy link

jamesla commented Apr 27, 2017

+1

@s01ipsist
Copy link

It would be good to document in the README but this is already supported through env vars.

AWS_PROFILE=test cfn-flow list

From http://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/credentials.html

Setting the AWS_PROFILE environment variable affects credential loading for all officially supported AWS SDKs and Tools 

@et304383
Copy link

et304383 commented Feb 7, 2018

This is a rabbit hole. The environment variables are the preferred way to configure any of the AWS SDKs.

Imagine you use the Python SDK for your Flask app. Would you ask Flask to support a --profile parameter?

I know that's an extreme case because Flask isn't designed as a wrapper to the SDK, but the argument remains the same. Tools like this any various other tools designed to make our lives easier are just custom logic wrapping one of the various AWS SDKs. The SDKs support certain methods for configuration and the least invasive method is the environment variables.

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

No branches or pull requests

4 participants