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

Compatibility with vagrant-aws #64

Closed
anthoc opened this issue Oct 6, 2020 · 4 comments
Closed

Compatibility with vagrant-aws #64

anthoc opened this issue Oct 6, 2020 · 4 comments
Labels

Comments

@anthoc
Copy link

anthoc commented Oct 6, 2020

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

@apatard
Copy link
Member

apatard commented Oct 7, 2020

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.

@anthoc
Copy link
Author

anthoc commented Oct 8, 2020

Hi @apatard. Thank you for your answer.
I'm new to molecule and I discovered recently that it is possible to create my own "driver" using the delegated driver, so in the meantime I'll work on this, or use the molecule-ec2 driver.
But I hope the problem will we resolved soon for the community. :)

Thank you again

@apatard
Copy link
Member

apatard commented Dec 16, 2020

@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 ?
Thanks!

@ssbarnea ssbarnea transferred this issue from ansible-community/molecule-vagrant Jan 6, 2023
@apatard
Copy link
Member

apatard commented Jan 11, 2023

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

@apatard apatard closed this as completed Jan 11, 2023
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

2 participants