Skip to main content
Version: 9.x (Current)

CRUD Service Configuration

This service can be added to your project by visiting Mia-Platform Marketplace and creating a new microservice from the CRUD Service plugin.

Configure a CRUD Service to use MongoDB CRUD section

In order to start using the MongoDB CRUD section, all you have to do is adding it from the Marketplace: all the ConfigMaps and environment variables it needs will be precompiled with no need to change them.


The CRUD Service supports custom CA certs. If you want to learn more about these certificates and how to configure them in your CRUD Service visit this page


The CRUD Service default configmap is mounted in /home/node/app/collections. You can freely choose its name during the service creation.

Furthermore, the ConfigMap is not editable, as it is fundamental for the MongoDB CRUD section to work: it is not possible to add files, edit the mountPath or delete it.

However, you will find a link that will redirect you to MongoDB CRUD dedicated section where you can continue to configure your project CRUDs. By doing so, you will automatically define the collections that will be handled by the service, which means that there is no need to add any configuration files.

Environment variables

  • MONGODB_URL (required): the MongoDB connection string;
  • COLLECTION_DEFINITION_FOLDER (required, default /home/node/app/collections): the path to the folder where all collections are defined;
  • USER_ID_HEADER_KEY (required): header key used to know which user makes the request. User id is useful to add creatorId and updaterId field in collection document;
  • CRUD_LIMIT_CONSTRAINT_ENABLED: (default: true): a boolean value to enable the query limit constraint feature. If it is enabled, the max limit of the get list APIs is 200.
  • TRUSTED_PROXIES (default:,, the string containing the trusted proxies values.
  • HTTP_PORT: The port exposed by the service.
  • LOG_LEVEL (default: info): level of the log. It could be trace, debug, info, warn, error, fatal.
  • EXPOSE_METRICS (default: false): boolean that specifies if prometheus metrics should be exposed or not.