Config file path command line argument

[carlosreyna-plated]

Is your feature request related to a problem? Please describe.
We have multiple AWS accounts we interact with and would like to be able to specify a config.properties file through a command line argument.

Describe the solution you'd like
Something like the example below.

java -jar ~/.okta/okta-aws-cli-2.0.0.jar --config=~/aws1-config.properties <command> <args>

Describe alternatives you've considered
We are open to options on how to specify configuration files.

[junkangli]

Since the issue raised is basically regarding support of multiple AWS accounts, you may want to discuss it in #304.

[carlosreyna-plated]

Since the issue raised is basically regarding support of multiple AWS accounts, you may want to discuss it in #304.

Looked at it and it is a painful workaround. I strong believe this is a better approach. It would allow users to select different OKTA accounts and configurations without modifying their file repeatedly. It is also something that should be simple to achieve.

[jeremyplichtafc]

With #331 which was just released in v2.0.4 it will now load ~/.okta/config.properties then ~/.okta/config.${OKTA_PROFILE}.properties.

So for example. Say you had a "stage" environment you wanted to load. You would put your common properties in ~/.okta/config.properties, then make a file with properties specific to your stage account in ~/.okta/config.stage.properties and run:

okta-aws stage s3 ls

this is equivalent to also running
OKTA_PROFILE=stage java -Djava.util.logging.config.file=~/.okta/logging.properties -classpath ~/.okta/okta-aws-cli.jar com.okta.tools.WithOkta aws --profile stage s3 ls

Can you give this a shot in latest release and let us know if it works for you?