This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
💖 looking for molecule ec2 driver maintainers #39
Comments
|
I’m going to need this driver soon, so happy to work on it as best as I can! |
|
i can also work. |
|
we are already using it very heavily, so will be happy to contribute. |
|
Count me in as well. |
|
Count me in 😄 |
ssbarnea
changed the title
|
I am still looking for people, please ping me on irc if you want to take it under your wing. |
|
Made it any of the volunteers into the maintainers? |
|
Invitation is still open and the fact the the project has 5 open PRs is not very good. I can help only when pull-requests are passing CI and anyone can contact me (zbr) on freenode #ansible-lint channel. Shortly, the invitation is still open. |
|
@gundalow Please restore my rights, so I can give others triage and later write access. |
|
I invited everyone involved in this thread to be a collaborator, initially with triage but I will boost it as soon I get some extra confirmation. |
|
sorry to bother with boring question but in this case what it's mean collaboration with triage ? |
|
Mainly it means you can open/close/edit issues. Once you do few reviews I will enable write access, which means ability to merge. There is only one older pull-request open which seems abandoned by OP, still, take a look at it and see if you can extract something useful out of it before we close it. I guess that once done, you will want me to help with a new release. Ping me and I will tag a new one if one of you can confirm that master code works fine with current release of molecule/ansible. |
|
Hey @ssbarnea, sorry to bother, but I completely neglected to ever ack the invite, but could have sworn I did. Would you mind sending another one? |
|
@jgoldschrafe Somehow I missed the reply, still interested? I sent the invite again. I observed that this repo lacked active maintenance for a very long time and I will have to drop it from the list of maintained plugins if nobody steps in to keep at least the CI green and compatible with newer versions of molecule. |
|
Anyone still interested in helping with maintenance of this plugin? I need some some help with review from people using this in production, especially as some proposed PRs have the potential of introducing regressions. |
|
I hope to submit several PRs soon and could probably help with the maintenance afterwards. (It will give you a chance to evaluate my skills, etc.) We're just starting to use molecule + ec2 at work so I wouldn't say this is a 'production' work - but I am using it to develop and maintain both my ansible scripts that manage dev and qa resources. |
…raw args Since molecule ansible/molecule#3887, the jinja is now autoescaping, which leads to things like: virtualbox.customize [&ansible-community#39;modifyvm&ansible-community#39;, :id, &ansible-community#39;--natdnshostresolver1&ansible-community#39;, &ansible-community#39;on&ansible-community#39;] in the Vagrantfile. Add some "safe" filters to solve this. Signed-off-by: Arnaud Patard <[email protected]>
src/molecule_plugins/vagrant/modules/vagrant.py: Add safe filter for raw args Since molecule ansible/molecule#3887, the jinja is now autoescaping, which leads to things like: virtualbox.customize ['modifyvm', :id, '--natdnshostresolver1', 'on'] in the Vagrantfile. Add some "safe" filters to solve this. Signed-off-by: Arnaud Patard <[email protected]>
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
I am unable to maintain this driver as I am not using it, so I am looking for maintainers.
I can keep providing support for CI and integration with molecule itself but not around driver specifics.
The text was updated successfully, but these errors were encountered: