Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement dynamic configuration service #390

Merged
merged 3 commits into from
May 10, 2024
Merged

Conversation

rinkp
Copy link
Member

@rinkp rinkp commented May 3, 2024

For some features, such as the one requested in GH-389, it is preferable if we can store a dynamic configuration through the database engine. This PR introduces a configuration service.

Reading config and default values has been implemented in the API health endpoint. Setting and unsetting is never used, but useful for testing:

$this->configService->setConfig(ConfigNamespaces::DatabaseApi, 'sync_paused', new DateTime());

$this->configService->unsetConfig(ConfigNamespaces::DatabaseApi, 'sync_paused');

@rinkp rinkp requested a review from tomudding May 3, 2024 21:41
@rinkp rinkp changed the title Implement dynamic configuration module Implement dynamic configuration service May 3, 2024
@rinkp rinkp requested a review from Aarhunt May 3, 2024 21:45
Copy link
Member

@tomudding tomudding left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can summarise this in just one word: awesome!

@rinkp rinkp merged commit f7ae1d1 into GEWIS:main May 10, 2024
4 checks passed
@rinkp rinkp deleted the feat/configmodule branch May 10, 2024 08:03
github-actions bot added a commit that referenced this pull request May 10, 2024
rinkp: Merge pull request GH-390 from 'rinkp/feat/configmodule'

Implement dynamic configuration service

Co-authored-by: rinkp <rinkp@users.noreply.github.com>
@rinkp rinkp mentioned this pull request Jul 11, 2024
5 tasks
tomudding added a commit to tomudding/gewisdb that referenced this pull request Aug 7, 2024
I am against having the names hard-coded in the e-mails. We previously discussed
in GEWISGH-286 that we do not have a better way of doing this, since then we have the
new dynamic configuration available that would solve this (GEWISGH-390) but would
still require updates each year to ensure the data is up-to-date.

Instead, we do a bit less personalisation and a bit more of not hard-coding
names and dates.
tomudding added a commit to tomudding/gewisdb that referenced this pull request Aug 7, 2024
I am against having the names hard-coded in the e-mails. We previously discussed
in GEWISGH-286 that we do not have a better way of doing this, since then we have the
new dynamic configuration available that would solve this (GEWISGH-390) but would
still require updates each year to ensure the data is up-to-date.

Instead, we do a bit less personalisation and a bit more of not hard-coding
names and dates.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants