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

Fix ANSIBLE_LIBRARY variable handling #3103

Merged

Conversation

tadeboro
Copy link
Contributor

@tadeboro tadeboro commented May 8, 2021

When we introduced the ability to pass down the user-specified ANSIBLE_LIBRARY variable value to the molecule, we wrongly assumed that the variable will always contain a single component, which is not always true.

This commit makes sure that we properly handle scenarios where users specify multiple directories in the ANSIBLE_LIBRARY environment variable.

Fixes #3083

PR Type

  • Bugfix Pull Request

@ssbarnea ssbarnea self-requested a review May 14, 2021 10:03
@ssbarnea ssbarnea added the bug label May 14, 2021
@ssbarnea
Copy link
Member

@tadeboro please rebase and thanks for addresing it.

When we introduced the ability to pass down the user-specified
ANSIBLE_LIBRARY variable value to the molecule, we wrongly assumed
that the variable will always contain a single componet, which is not
always true.

This commit makes sure that we properly handle scenarios where users
specify multiple directories in the ANSIBLE_LIBRARY environment
variable.
@tadeboro tadeboro force-pushed the fix-ansible-library-construction branch from fd7c4be to c6eb282 Compare May 14, 2021 11:57
@ssbarnea ssbarnea merged commit 14e7575 into ansible:master May 14, 2021
@tadeboro tadeboro deleted the fix-ansible-library-construction branch May 14, 2021 12:06
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.

Current directory being inadvertently added to ANSIBLE_LIBRARY
2 participants