RHEL 7 EOL is approaching (June 2024) and we still have some services running on RHEL7 machines.
github2fedmsg is of these services and we need to do something about it.
Current state of things:
ARC investigation document
Recommendation was to replace it with more general solution webhook2fedmsg
webhook2fedmsg
June 2024
Metadata Update from @zlopez: - Issue assigned to abompard
This is submitted as outreachy project with @abompard as potential mentor.
The outreachy project started this week. @ghostle is the one who will be working on webhook2fedmsg :thumbsup:
Checking in on progress as we're close to the expected done date.
The outreachy project isn't close to being usable at this stage, we may need to keep github2fedmsg running for a couple months, if it's not too much of a problem. Otherwise me or @ryanlerch can try to port it quickly (and partially) to make the main part work on RHEL9 until the replacement is ready.
I'd really prefer we move it off rhel7... if you could do a quick port of it that would be nice.
Note that it might currently be broken to adding new projects: https://pagure.io/fedora-infrastructure/issue/11911
the main issue here with a quick 1:1 port is that it is using the velruse library (very old and unmaintained) to create webhooks (and other stuff) on github.
What we could in theory do, however, is disable the web interface, and just listen for existing webhook calls from the projects that already have it set up.
I'm for disabling the web interface, it didn't work well for some time anyway. We just need to probably replace the page with some info, why it's not working anymore.
It actually does work... the problem reported was a issue with permissions on the github side. ;(
Is there any way we can see how many new repos have been added when? if there's not too many being added, I'd be ok just announcing it will be blocked for a short time. Or perhaps we could come up with an interem way to manually enable? ie, ask people just to file tickets until we get the web side working again?
Any update? :-)
We should really push this now and announce that we are getting the github2fedmsg down. We should announce it on announce list and by small blog post.
@abompard Do you want to take care of that?
bump
@zlopez : I'm still investigating a Mirrormanager issues, do you mind doing the blog post please?
@abompard Let me prepare something
The announcement of github2fedmsg sunset was sent to:
The sunset date was announced to 3rd February, first Monday in February.
Log in to comment on this ticket.