Create new table for tracking private project creation/deletion

To have better oversight over private projects created, we should track their creation in a database. When created, a new entry would be populated containing the user ID, the project ID, and the date created. There should be a few extra columns that will be populated when the project is triggered for deletion as well which will help give us better insight into these projects. Below are the columns I'm initially thinking of tracking:

Name	type	Is PK	Nullable
userId	varchar(63)	X	N
projectId	int(10)	X	N
projectPath	varcahr(255)	X	N
parentProject	int(10)		Y
dateCreated	datetime		N
dateDeleted	datetime		Y

added statetodo label

assigned to @zacharysabourin

marked this issue as related to #78 (closed)

marked this issue as related to #80 (closed)

changed the description

changed the description

changed the description

changed the description

added statewip label and removed statetodo label

changed the description

added to epic eclipsefdn/it&5 (closed)

mentioned in commit 5687d338

mentioned in merge request !103 (merged)

added statereview label and removed statewip label

@malowe After looking into the Gitlab documentation, it became apparent that the userId that we would most likely want to store should be the Gitlab userId. Seeing as the Gitlab email and username are more likely to change. As such, I will change the userId table field to an int for the time being to continue with development.

This can be queried through https://gitlab.eclipse.org/api/v4/projects/{id_received_from_event} and then taking the creator_id field from the response. We can then query https://gitlab.eclipse.org/api/v4/users/{userId} if we need to figure out who the user is.

Yuck. The more I dig into the API layer of Gitlab, the grosser and grosser it gets. This works for projects created in a users namespace, but may not work if created in a group. In the Gitlab API, the owner and creator fields aren't distinct, and aren't accurate to what they might indicate from what I can tell. In the case of the project API samples, the creator is being used as a synonym for the owner of the entity and doesn't seem to indicate a separate user, so this may not be reliable.

Can you confirm if this is the case? If you have the API and hooks set up this shouldn't take too long to validate. If creator is a synonym for owning entity, rather than indicating who created this it will make this entry much stickier. We can figure out how to track this once we know a little more.

It works for both group and user namespaces.

mentioned in commit 468576b2

mentioned in commit c276e092

closed with merge request !103 (merged)