Migrate Relationship endpoints from Drupal

There are still additional endpoints to migrate under the account/profile/{username} path. Some of these paths include: /projects, /eca, /forum, /mailing-list, and /gerrit

The spec: https://api.eclipse.org/#operation/ProjectRelationship

The service will most likely need to connect to the Gerrit API, as well as make use of our mailing-list-api.

added Feature Request MBO prioritymedium statetodo team:webdev labels

assigned to @zacharysabourin

added to epic eclipsefdn&25 (closed)

added #27 (closed) as child task

added #28 (closed) as child task

added #29 (closed) as child task

added #31 (closed) as child task

added #32 (closed) as child task

added #33 (closed) as child task

added #34 (closed) as child task

For some reason, the /ECA one is not documented in our API docs.

added statewip label and removed statetodo label

/projects will require the /people/projects/full endpoint to be set up in fdndb-api. The data returned here is a mix of People, Projects, and Sys_relations data.

To determine whether a project has the specification_project flag set:

• DB table: eclipse_api_projects_spec_projects needs to be queried for projects
• Check if project_id is in spec project list

DDL

/mailing-list should be as simple as calling the mailing-list-api.

However, in its current form, this will introduce some circular calls.

Calling api.eclipse.org/foundation/mailing-list?username={name} makes a call to fetch the profile info from the profile service, gets the email field and then queries the DB to serve the data. https://gitlab.eclipse.org/eclipsefdn/it/api/eclipsefdn-mailing-lists-api/-/blob/main/src/main/java/org/eclipsefoundation/mailing/resources/MailingListsResource.java#L69

@cguindon @malowe I'm wondering if it makes sense to allow fetching mailing-list subscriptions directly via email? This would avoid the additional call back to the profile-api

I don't see how this is a cyclic call. account/profile/{username}/mailing-list will hit /foundation/mailing-list?username={username}, which will ask account/profile/{username} for the user profile for look-ups. While you link to the mailing-list relation URL in the base endpoint, the information isn't included so this should be safe.

mentioned in merge request !11 (merged)

/gerrit logic is here: https://gitlab.eclipse.org/eclipsefdn/it/websites/drupal/eclipse_api/-/blob/7.x-1.x/resources/gerrit.inc

It seems to be checking a DB table and then calling the Gerrit API if there is no records for the user. It then adds the gerrit data to the db table.

https://git.eclipse.org/c/www.eclipse.org/eclipse.org-common.git/tree/classes/rest/gerritApi.class.php

/forum logic is here: https://gitlab.eclipse.org/eclipsefdn/it/websites/drupal/eclipse_api/-/blob/7.x-1.x/resources/forum.inc

Forum feature is being deprecated and not migrating from Drupal

+1

added statereview label and removed statewip label

mentioned in issue #46 (closed)

mentioned in issue #48 (closed)

There is also a relationship endpoint for blobs that is not currently enabled on production. It will not be included in this migration.

+1

The relationship endpoints are ready for sign-off!

The following endpoints are enabled and ready on staging:

• /sandbox/account/profile/{username}/eca
• /sandbox/account/profile/{username}/gerrit
• /sandbox/account/profile/{username}/mailing-list
• /sandbox/account/profile/{username}/projects

The OpenAPI spec

@cguindon I will schedule a call for later this week to go over this. Feel free to poke at these whenever you have the time and let me know what you think. Do not hesitate to bring up any questions or concerns.

added statedone label and removed statereview label

closed

removed statedone label