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

AWS ENV vars not honored #17

Closed
joegoggins opened this issue Sep 27, 2013 · 3 comments
Closed

AWS ENV vars not honored #17

joegoggins opened this issue Sep 27, 2013 · 3 comments
Labels

Comments

@joegoggins
Copy link

It doesn't appear that AWS ENV vars are honored as described in README.
Even with the env vars set or by doing the following:

aws_access_key_id: <%= ENV['AWS_ACCESS_KEY'] %>
aws_secret_access_key: <%= ENV['AWS_SECRET_KEY'] %>
aws_ssh_key_id: <%= ENV['AWS_SSH_KEY_ID'] %>

I get this error:

-----> Starting Kitchen (v1.0.0.beta.3)
>>>>>> ------Exception-------
>>>>>> Class: Kitchen::UserError
>>>>>> Message: Kitchen::Driver::Ec2<default-centos-64>#config[:aws_access_key_id] cannot be blank
>>>>>> ----------------------
>>>>>> Please see .kitchen/logs/kitchen.log for more details
@fnichol
Copy link
Contributor

fnichol commented Nov 30, 2013

If you're still having this issue, could I ask that you upgrade Test Kitchen to at least 1.0.0.rc.1 and run kitchen list --debug to see what the resolved values for your keys are? Thank you!

@sethvargo
Copy link
Contributor

Ohai! I've just tested your use case with the latest Test Kitchen and Kitchen EC2 driver and was unable to reproduce your error. If you are still encountering this error, please reopen this issue and include the output of kitchen diagnose.

@joegoggins
Copy link
Author

Thanks for looking into it, will let you know if I have troubles after upgrading.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants