Skip to content

Conversation

@ssbarnea
Copy link
Member

@ssbarnea ssbarnea commented Feb 20, 2020

Instead of looking for config file only in user home, molecule will
now also look in current VCS repository.

This will enable people to add configs that are repository wide.

Due to its special naming .config/molecule/config.yml, there are
no real risks of breaking user configs.

Partial-Fix: #2565

Instead of looking for config file only in user home, molecule will
now also look in current VCS repository.

This will enable people to add configs that are repository wide.

Due to its special naming `.config/molecule/config.yml`, there are
no real risks of breaking user configs.
@ssbarnea ssbarnea self-assigned this Feb 20, 2020
@ssbarnea ssbarnea requested a review from sshnaidm February 20, 2020 15:27
@ssbarnea ssbarnea added this to the 3.0.1 milestone Feb 20, 2020
@ssbarnea ssbarnea marked this pull request as ready for review February 20, 2020 15:38
@ssbarnea ssbarnea changed the title Load molecule config from VCS is possible Load molecule config from VCS if possible Feb 20, 2020
@ansible-zuul
Copy link
Contributor

ansible-zuul bot commented Feb 20, 2020

Build succeeded.

@ssbarnea ssbarnea added the gate label Feb 20, 2020
@ansible-zuul
Copy link
Contributor

ansible-zuul bot commented Feb 20, 2020

Build succeeded (gate pipeline).

@ansible-zuul ansible-zuul bot merged commit d5b7599 into ansible:master Feb 20, 2020
@ssbarnea ssbarnea deleted the fix/vcs-config branch April 8, 2020 08:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

ability to define implicit preparing command at repository level

1 participant