Create a POST endpoint for system hooks to inspect new private projects

When we enable new private projects, we want to ensure that projects created are forks associated with a repository and not bare repositories with code unrelated to Eclipse projects. To that end, we will want to accept system hook events to receive project_create events and inspect the created project.

Once we receive a system hook call, we need to verify the event type and then cast the data to the proper request type. This is required as Gitlab does not allow for scoping which system events can or cannot create webhook calls. An additional note is that the endpoint should reflect this and be a generic path, such as /git/webhooks/gitlab/system. This hook should trigger a queued event in an executor as we don't want to block the request while we validate the data (the hook doesn't accept responses, so we don't want to lock up system resources for no reason).

As the project creation event does not include information about whether a project is a fork, we will have to callback to Gitlab to read this information. We should consider using a Gitlab lib like Gitlab4J to simplify some of the writing of code and reduce maintenance costs. We should then inspect the data that we get back about the new project, and check if we should delete.

Conditions for deletion:

• Project is private
• Project is in a users namespace
• Project has no forked from/parent repo data

@mbarbero are there any other conditions we want to observe for deleting private projects? I think this covers what we will need for the MBO.

added Enhancement MBO statetodo labels

assigned to @zacharysabourin

Well, before thinking about automated deletion on creation, we want to store the information about the private projects being created. See eclipsefdn/helpdesk#1717 (closed).

From the stored data, we want to have some kind of batch job that will remove "old" (how old is TBD) automatically. See eclipsefdn/helpdesk#1716 (closed)

The automated deletion of unused branches is set in eclipsefdn/it/webdev/eclipsefdn-vc-tools#223 (closed), to take advantage of our caches and already existing job!

marked this issue as related to eclipsefdn/it/webdev/eclipsefdn-vc-tools#223 (closed)

marked this issue as related to #79 (closed)

marked this issue as related to #80 (closed)

To add clarification, we will be scrapping the early automated deletion portion of this issue. As we don't anticipate using this service to host external code immediately at least, it's better to investigate actual first. This way we can create targeted business rules rather than guess what people will do.

Additionally, if this request is done separately from the DB persistence layer issue, then the first iteration should just post the information to the logs. This way we can test the output without having to necessarily stop development. If done separately, a new issue will need to be created to integrate the 2 issues.

added statewip label and removed statetodo label

added to epic eclipsefdn/it&5 (closed)

mentioned in commit 304ea7aa

mentioned in merge request !103 (merged)

mentioned in commit c9f6f691

added statereview label and removed statewip label

mentioned in commit c276e092

closed with merge request !103 (merged)

marked this issue as related to eclipsefdn/helpdesk#1717 (closed)