Dynamic Configuration with Admin Page + Artemis Teams

[GODrums]

Motivation

To accomodate for long-running production deployments, we want to be able to change the application configuation during runtime while keeping it persistent.
Instead of separating the leaderboard via repositories, we want to group users teams to acknowledge cross-repository development.

Description

• Dynamic Configuration
  • Add persistent entity for application (server) config
  • Endpoints to access config in client
  • Rework meta endpoint with dynamic config
• Admin Page /admin
  • Display and edit current config values
  • Rework UI elements with Spartan
  • Create nav-bar / side-menu for admin sub-pages
• Artemis Teams
  • Create Team entities with dynamic members
  • Allow re-assigning members in admin page /admin/users
  • UI for adding / deleting teams
  • Add teams-filter to leaderboard
  • Automatic team assignments via PR activity

Follow-Ups

Refer to #160

Testing Instructions

1. Start the application-server and webapp
2. Login with your Github account (make sure it has the 'Admin'-role in Keycloak)
3. Click on "Admin" in the top nav-bar
4. Try changing some of the values in the admin area, such as the list of monitoried repositories
5. Restart the application-server and control if your changes were persisted

Screenshots (if applicable)

Checklist

General

• PR title is clear and descriptive
• PR description explains the purpose and changes
• Code follows project coding standards
• Self-review of the code has been done
• Changes have been tested locally
• Screenshots have been attached (if applicable)
• Documentation has been updated (if applicable)

Client (if applicable)

• UI changes look good on all screen sizes and browsers
• No console errors or warnings
• User experience and accessibility have been tested
• Added Storybook stories for new components
• Components follow design system guidelines (if applicable)

Server (if applicable)

• Code is performant and follows best practices
• No security vulnerabilities introduced
• Proper error handling has been implemented
• Added tests for new functionality
• Changes have been tested in different environments (if applicable)

[iam-flo]

Too large to review

[iam-flo]

I dont like the textfield. Its is small and not easy to use, maybe we could have the repositories in a list of textfields, where you can edit each

[GODrums]

Indeed, I should refactor this. At this point the PR is huge again, and there's so much stuff that could still be improved.

[iam-flo]

if we cant edit the teams color, why have it in the table

[GODrums]

Yeah, it should probably be editable.
I personally would prefer doing follow-up PRs for stuff like this to avoid keeping the same PR open for many weeks.

[iam-flo]

yes thats fine, then we just need to collect all points in a new issue so we dont forget some. :)

[iam-flo]

label maybe clickable for removal

[iam-flo]

We also need a LiquiBase:diff changeLog I think.

[GODrums]

We also need a LiquiBase:diff changeLog I think.

Could you give me a quick overview for the workflow regarding Liquibase?

I assume npm run db:changelog:diff is required for the merge, but does that file need to be commited too or is everything executed on the prod-server?

[FelixTJDietrich]

We also need a LiquiBase:diff changeLog I think.

Could you give me a quick overview for the workflow regarding Liquibase?

I assume npm run db:changelog:diff is required for the merge, but does that file need to be commited too or is everything executed on the prod-server?

This file should be renamed and commited + added to the history. Please compare it with the Artemis codebase. If we don't commit it the server will not update its schema. In the future we can squash the changelog again if it gets too long.