Skip to content

Fix vagrant module in playbooks#314

Open
0x4D616E75 wants to merge 7 commits intoansible-community:mainfrom
0x4D616E75:fix-vagrant-playbooks
Open

Fix vagrant module in playbooks#314
0x4D616E75 wants to merge 7 commits intoansible-community:mainfrom
0x4D616E75:fix-vagrant-playbooks

Conversation

@0x4D616E75
Copy link
Copy Markdown

@0x4D616E75 0x4D616E75 commented Jun 23, 2025

This PR fixes change only the module name to the fqdn of the module and fix #301

additional commits fixes the tests

# Conflicts:
#	.ansible-lint
#	conftest.py
#	test/vagrant-plugin/functional/test_func.py
@0x4D616E75
Copy link
Copy Markdown
Author

Hi @ssbarnea,
I have merged the main branch and resolved all conflicts. Could you please review the pull request again?
The failed tests are not related to my changes and concern the Azure and Podman plugins.

@paulkitt
Copy link
Copy Markdown

@ssbarnea @0x4D616E75 Any updates here? Would be so great to get this problem fixed and a working molecule vagrant setup back

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

"couldn't resolve module/action 'vagrant'" error when installing molecule-plugins in a fresh environment

3 participants