Closed kwellman closed 8 years ago
Hm, I'm not sure I like using --username
for this. It's a strange name to use, and we'd only be using it because it's all that Lektor gives us today.
Instead, I think it would be better to store this in a plugin configuration file, or maybe even in the .lektorproject
file under the [servers] section as a new key-value pair.
Another option would be making a change to Lektor to allow adding additional credential fields in the deploy command.
What do you think?
FYI, while we discuss this - AWS_PROFILE=whatever lektor deploy
will work since boto will respect the env var.
Yeah. --username is a little odd and confusing. I think just setting the environment variable from the command line might by the way to go.
Okay, glad you agree. I've added some documentation to the README to point out that AWS_PROFILE is a good way to do this; I'm going to close this PR.
Is setting the AWS_PROFILE available in the .lektorproject
file?
For people who use profiles in their .aws/credentials to handle multiple accounts, this pull request adds the ability to specify the profile name using the --username parameter. If parameter not set, default profile will be used.