-
-
Notifications
You must be signed in to change notification settings - Fork 57
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
Deprecation request. #213
Comments
I've not worked on it for a bit as I changed companies. I don't think it was in that bad a shape though, and I don't know of any better replacement. ProxySQL itself is still actively developed, so I'm not keen on deprecated this. I think it'd make it much harder for anyone using the module to contribute. #191 wasn't that long ago either. As for the current test failures, has anyone got an idea about Oracle Linux failing? I vaguely recall seeing similar failures in a different module. Can't remember where though... |
Last release was 2021 though |
yeah, so if we can fix the tests, modulesync and get a release out, that'd be great. There was even an offer of help in #195 and several thumbs up from other people who would like to see it too.
Is the error. Since we've not had a release in years, I'd also hold back on removing any EOL OSes until after a release has been made. |
I'm actively using this module and I'm happy to spend some time on it, but can't tell, when this will be possible. :( |
will fix some errors, but there are more. I'll try to work on it this or next week to get the Besides that, I guess it makes sense to stop supporting old versions of proxysql. Currently, 2.2 to 2.7 are maintained. |
Well...
Any good way to solve this? Setting it to |
@TheMeier As people (like me) are still relying on this module and I'm trying to get it as good as possible, I think we can close this request? |
This module looks abandoned, we should consider deprecating it.
The text was updated successfully, but these errors were encountered: