-
Notifications
You must be signed in to change notification settings - Fork 34
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
Switch to become plugins #29
Conversation
I have tried using this patch, since I'm running into rpoblems with ansible 2.8, but it's not working for me. I get this error:
|
I followup to myself, to state, I actually got that error because I forgot the "become" flag, so no become plugin was present, as the error states. If I pass the "-b" flag(or have become: yes in the play) everything works. Maybe adding a check for this condition could be useful. |
BTW this PR works brilliantly. @austinhyde if you're not actively using this we could move it to a "freebsd community" fork? |
My apologies for the terribly long time without a response. It's true that I am no longer using this project, and no longer have any "real" machines to test against, which has made accepting PRs much more onerous than it used to be. Fortunately, I've recently had some time to set up Vagrant (now on master), which should allow much easier testing of PRs. In this case, I was able to confirm that this PR
This PR aside, in response to @dch - I would definitely be open to transferring this to someone else that's more actively using it or some sort of community organization. If no one is willing to take that on or has ideas on where this can live, I can continue to steward the project, and make some of you co-maintainers. Thoughts? |
I would not be able to be a maintainer for the project because I am not a python programmer, I know the language only superficially. But I'd like to add it to the official FreeBSD ports tree. It would be much easier if a new release was cut from it here on github to use as a basis. |
No description provided.