Mobicoop V3 - Configuration Service

Configuration items management. Used to configure all services using a broker to disseminate the configuration items.

This service handles the persistence of the configuration items of all services in a database, and sends values via the broker.

Each item consists in :

• a uuid : a unique identifier for the configuration item
• a domain : each service is associated with one or more domains, represented by an uppercase string (eg. USER)
• a key : the key of the configuration item (a string)
• a value : the value of the configuration item (always a string, each service must cast the value if needed)

This service centralizes the configuration items, but theoratically each service should "push" its items toward the configuration service.

Practically, it's the other way round as it's easier to use this configuration service as the single source of truth. This is why configuration items key and domain are immutable : services may use hardcoded domain-key pairs. Therefore, only values can be updated.

Available domains

• AD : ad related configuration items
• MATCHER : matching algotithm related configuration items
• USER : user related configuration items

Requirements

You need Docker and its compose plugin.

You also need NodeJS installed locally : we strongly advise to install Node Version Manager and use the latest LTS version of Node (check that your local version matches with the one used in the Dockerfile).

The API will run inside a docker container, but the install itself is made outside the container, because during development we need tools that need to be available locally (eg. ESLint, Prettier...).

A RabbitMQ instance is also required to send / receive messages when data has been inserted/updated/deleted.

Installation

• copy .env.dist to .env :

  cp .env.dist .env
  

  Modify it if needed.

• install the dependencies :

  npm install
  

• start the containers :

  docker compose up -d
  

  The app runs automatically on port 5003.

Database migration

Before using the app, you need to launch the database migration (it will be launched inside the container) :

npm run migrate

Usage

The app exposes the following gRPC services :

• Get : get a configuration item by its domain and key

  {
      "domain": "AD",
      "key": "seatsProposed"
  }
  

• Set : create or update a configuration item

  {
      "domain": "USER",
      "key": "key1",
      "value": "value1"
  }
  

• Delete : delete a configuration item by its domain and key

  {
      "domain": "AD",
      "key": "seatsProposed"
  }
  

• Propagate : propagate all configuration items using the message broker

  {}
  

Messages

As mentionned earlier, RabbitMQ messages are sent after these events :

• Set (message : the created / updated configuration item informations)

• Delete (message : the uuid of the deleted configuration item)

• Propagate (message : all the configuration items)

Various messages are also sent for logging purpose.

Tests / ESLint / Prettier

Tests are run outside the container for ease of use (switching between different environments inside containers using prisma is complicated and error prone). The integration tests use a dedicated database (see db-test section of docker-compose.yml).

# run all tests (unit + integration)
npm run test

# unit tests only
npm run test:unit

# integration tests only
npm run test:integration

# coverage
npm run test:cov

# ESLint
npm run lint

# Prettier
npm run pretty

License

Mobicoop V3 - Configuration Service is AGPL licensed.