Migrate ECA GitHub validation to Quarkus
This is an MBO for Q1. The objective for this MBO is to migrate the webhook functionality for the Eclipse ECA Validation GitHub APP from Drupal (accounts.eclipse.org) to this project.
Also included are the validation pages such as https://accounts.eclipse.org/legal/eca/validation/126686. They need to be migrated to this application.
@malowe Can you please break down this initiative into smaller tasks or issues for everything that you think we will need to accomplish such as but not limited to deploying to production and defining a plan on how we are going to deal with backward compatibility, testing...?
Designs
Is blocked by
Relates to
Activity
added MBO prioritymedium severitynormal team:webdev labels
marked this issue as blocked by #98 (closed)
Most of the remaining tasks have been defined in #98 (closed), so I can create an issue to handle revalidation logic which is the last task to accomplish before we can start the final process of testing and switching over.
We had originally discussed migration mixed among calls, other issues, and slack, so I'll reiterate our then decisions here. We were not going to be migrating any content explicitly. These checks only live for 6 months, so there was planned to be a graceful degradation period where we allow old checks to naturally run their course after the switchover. Any checks that would be triggered from the old ECA window after migration would automatically be sent to the new application and would begin to respond as a request to the new application with a new URL. If there are any cases of people checking ECA statuses 6 months past initial creation that is also not still active, we can discuss this but I think that this would create a lot of work and server processing for very little, if any, gain.
Most of the remaining tasks have been defined in #98 (closed), so I can create an issue to handle revalidation logic which is the last task to accomplish before we can start the final process of testing and switching over.
Agree that most of the tasks are listed here. The only thing that I see missing here is a task about updating the webhook URL in our Github APP: https://github.com/apps/eclipse-eca-validation.
In the end, this is how I am going to measure success for this MBO. This MBO will be completed once the webhook URL for the APP is updated to point to our git-eca-rest-api API service.
We had originally discussed migration mixed among calls, other issues, and slack, so I'll reiterate our then decisions here.
This is the point of these exercises. We need to capture decisions in issues. I would like to see an issue about the migration topic. Please include your recommendation on what we should do and why (technical limitation and/or too much effort...).
Once that is done, I will like to share this with some folks to ensure that everyone is o.k with our plans.
Edited by Christopher Guindon
marked this issue as related to #116 (closed)
added #117 (closed) as child task
General plan:
- Finish testing and deploying #98 (closed) by end of Jan, awaiting review atm.
- Begin task of revalidation button in early Feb (#116 (closed)), goal to be up for review by the 15th, and live by the 22nd
- Final testing from Feb 22nd to Feb 29th using test app hooked to webdev sandbox
- Switch over and monitor March 1st to the 8th (#117 (closed))
added statetodo label
assigned to @malowe
marked this issue as blocked by #122
marked this issue as related to #123 (closed)
marked this issue as related to #124 (closed)
marked this issue as related to #125 (closed)
marked this issue as related to #113 (closed)
mentioned in merge request !151 (merged)
mentioned in commit 1f3ec1b1
mentioned in commit 789ba5e6
added statereview label and removed statetodo label