search

ansible-community / molecule-plugins

Collection on molecule plugins
MIT License
109 stars 73 forks source link

Compatibility with vagrant-aws #64

Closed anthoc closed 1 year ago

anthoc commented 3 years ago

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 commented 3 years ago

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 https://github.com/ansible-community/molecule-vagrant/pull/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 commented 3 years ago

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 commented 3 years ago

@anthoc current master branch has https://github.com/ansible-community/molecule-vagrant/commit/0c1aed1fb550a49cf584104a005aab1d67afc014, 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!

apatard commented 1 year ago

There has been no activity on this bug for quite some time and according to https://github.com/mitchellh/vagrant-aws/issues/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