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

Function Service

The function service lets you map code to endpoints without provisioning a fully-fledged dedicated microservice.

You can create several function services within the same DevOps Console project. You have to create the scripts both for local and remote unit testing only for the first function service. The subsequently created ones will share the same scripts.


The following steps will walk you through the setup of the needed scripts.

Run the function service locally

You can locally start the function service to test and develop the handlers without the need of deploying to the cloud.

To run the function service clone the DevOps Console project and add the script. Remember to add execution permissions with chmod +x

Unit testing and continuous testing

Every function service handler should be bundled with unit tests. The tests should be started locally, before each commit. To achieve continuous testing we provide a Gitlab's pipeline stage to remotely run the unit tests.

To setup the unit testing add the script in the configuration root. Remember to add execution permissions with chmod +x

To setup continuous testing you should append the following pipeline stage to the .gitlab-ci.yml file.

stage: release
image: docker:19.03.12


- docker:19.03.12-dind

- docker info
- docker login -u ${NEXUS_USER} -p ${NEXUS_TOKEN} ${NEXUS_URL}

coverage: '/^Statements\s*:\s*([^%]+)/'

- ./


The setup phase is over.

Create a function from the Console

To deploy a new function service, open the Console add a new microservice choosing the docker image

Then, create a new configuration for this microservice and call it as you wish, (e.g.: my-function-service). Type /home/node/app/functions as run-time mount point.

To add a new endpoint to the function service, click on Add file, call it as you prefer (e.g.: hello.js) and type the JavaScript code. It must export the following required fields:

  • method: Request method (e.g. POST, GET, PATCH ...)
  • path: Endpoint path (e.g. /hello-world)
  • name: Friendly name for this function.
  • handler: The function executed when the endpoint is reached.
  • schema: JSON schema for the request and reply. The format is the one accepted by Fastify.

Libraries already included as dependencies:

  • lodash
  • fs
  • split2
  • mississippi
  • nanoid

In order to import the nanoid library you need to use the library "fix-esm". Following an example

const { nanoid } = require('fix-esm').require('nanoid')

Warning! You have to create the function file from the Console, not from the project repository.


Every time you change the function code (either from the Console or the repository) you should 'commit and regenerate'

hello.js example:

'use strict'

const schema = {
body: {},
response: {
'200': {
type: 'object',
properties: {
'text': {type: 'string'},

async function handler(req, res) {
'text': 'hello-world',

module.exports = {
method: 'POST',
path: '/hello-world',
name: 'Hello World',

Now click Commit & deploy, the newly created endpoint will be exposed and testable right away.

The env FUNCTIONS_FOLDER holds the path to the directory containing the definitions of the functions, you are free to customize it and mount there any function. When FUNCTIONS_FOLDER is not specified it defaults to /home/node/app/functions. Anyway, you should always create the FUNCTIONS_FOLDER directory using the "Add configuration" feature on the Console in order to have it correctly mounted on the microservice.

Run the function service locally

To test the function service locally, clone the Console configuration repository, then run the script in the configuration root named

Add as extra argument the name of the function-service you want to bootstrap (e.g.: ./ config-map-my-function-service).

Unit testing


To set up unit tests of your endpoints, clone the Console configuration repository and create a directory to hold the tests. It must follow the naming convention: test/config-map- %function-service-name% (e.g.: test/config-map-my-function-service). In this directory, you can place the unit test files whose name must end with .test.js

Create a test

Example: test/config-map-my-function-service/index.test.js

'use strict'

const t = require('tap')
const lc39 = require('@mia-platform/lc39')

async function setupFastify(envVariables) {
const fastify = await lc39('./index.js', {
logLevel: envVariables.LOG_LEVEL,
return fastify

t.test('functions-service', async t => {
const fastify = await setupFastify({
LOG_LEVEL: 'trace',
FUNCTIONS_FOLDER: __dirname + '/../functions',

t.teardown(async() => {
await fastify.close()

const getResponse = (url, body) => {
return fastify.inject({
method: 'POST',

t.test('test function is correctly executed', async t => {
const url = '/hello-world'
const mockResponse = {
'text': 'hello-world',
const res = await getResponse(url, {})

t.strictSame(res.statusCode, 200)
t.strictSame(JSON.parse(res.payload), mockResponse)


Run the tests (locally)

To run the tests locate the file in the configuration root named

Running this script will execute the tests for each function-service. You can add an extra argument with the test directory name to run the tests against a single function service (e.g.: ./ config-map-my-function-service)

Run the tests (from Gitlab pipeline)

You can trigger this pipeline from the CI/CD > Run Pipeline Gitlab's menu setting the variable RUN_INTEGRATION_TESTS to TRUE