-
Notifications
You must be signed in to change notification settings - Fork 76
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
Compatibility with vagrant-aws #64
Comments
Hi, in theory, it should work with every vagrant provider. In practice, with the current code, it has few chances to work, which is sad. There's been some work to correct that in ansible-community/molecule-vagrant#31 but it has been blocked mainly by CI issues. I hope that the CI issues will be solved soon and that work on this PR will resume. Once this PR merged, I hope you'll be able to use vagrant-aws. |
Hi @apatard. Thank you for your answer. Thank you again |
@anthoc current master branch has ansible-community/molecule-vagrant@0c1aed1, which changed a lot the way the Vagrantfile is handled and the code "limitation" about vagrant providers should be solved. If you have some spare time, could you please test it with vagrant-aws ? |
There has been no activity on this bug for quite some time and according to mitchellh/vagrant-aws#579, the vagrant-aws driver is not maintained anymore, so I'm going to close this bug. If I'm wrong and that the bug is still valid, please tell us and the bug will be reopened |
Hello,
Do you think that the vagrant aws provider (https://github.com/mitchellh/vagrant-aws) can work together with the molecule vagrant module ?
Thank you
The text was updated successfully, but these errors were encountered: