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

Add support for custom driver name #3795

Merged
merged 3 commits into from
Jan 11, 2023

Conversation

gciavarrini
Copy link
Contributor

This PR aims to add support for using custom driver name.

The proposed solution patches the molecule.json schema to allow driver names starting with molecule_, molecule-, custom_, or custom-.

This PR adds tests for the proposed feature as well.

This commit adds support for custom driver names starting with
`molecule_`, `molecule-`, `custom_`, or `custom-`

Signed-off-by: Gloria Ciavarrini <gciavarrini@redhat.com>
Test if `molecule-`, `molecule_`, `custom-`, `custom_` are
valid prefixes as driver name.

Test that any other name fails the validation.

Signed-off-by: Gloria Ciavarrini <gciavarrini@redhat.com>
Signed-off-by: Gloria Ciavarrini <gciavarrini@redhat.com>
@gciavarrini gciavarrini marked this pull request as ready for review January 10, 2023 14:36
@gciavarrini gciavarrini requested review from a team as code owners January 10, 2023 14:36
@gciavarrini gciavarrini requested review from Shaps, jseguillon, ssbarnea, ganeshrn and shatakshiiii and removed request for a team January 10, 2023 14:36
@ssbarnea ssbarnea merged commit 27ebd36 into ansible:main Jan 11, 2023
@retr0h
Copy link
Contributor

retr0h commented Apr 3, 2023

Any idea when this PR will be included in a molecule release?

The changes to the molecule driver system has broken molecule drivers I maintain: retr0h/molecule-kind#2

@gciavarrini
Copy link
Contributor Author

Hi @retr0h !
It has been included in release v5.0.0a0

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.

3 participants