This repository has been archived by the owner on Jan 6, 2023. It is now read-only.
Migrate create.yml, destroy.yml and molecule_vagrant.py from molecule 2.22.0 #9
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@ssbarnea sorry that I have not much idea about where |
|
Build succeeded.
|
|
Build succeeded.
|
|
@hswong3i I already started working on this driver this morning. There is a huge number of changes need, and one problematic ones is the installation of vagrant module. You are better off doing anything else until I push these changes. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A quick and dirty workaround for create.yml, destroy.yml and molecule_vagrant.py.
TODO: This should create duplicated
libarary/molecule_vagrant.pyunder each molecule scenario directories which is not ideal.Fix #8