A config loader that loads vehicle information using .toml files
simple unittests for the config loader
A Dockerfile to build a container for the service
The REST Service has only boilerplate for Exception Handling and CORS configuration, no specific implementations / config.
The REST Service provides /status Endpoints to monitor the current status of the service.
The REST Service provides /v1 Endpoints to access its resources.
To access vehicles use /v1/consumption with a POST request and the following data:
{
"vehicle_name":"car"
}
An example curl command is in README file of the service. For curl you will need to escape any double quotes with a backslash (\").
The /status/alive and /status/ready currently return OK on the same conditions.
TODOs:
[x] Implement proper ready conditions for ready endpoint
The merge request includes:
The REST Service has only boilerplate for Exception Handling and CORS configuration, no specific implementations / config.
The REST Service provides /status Endpoints to monitor the current status of the service. The REST Service provides /v1 Endpoints to access its resources.
To access vehicles use /v1/consumption with a POST request and the following data:
An example curl command is in README file of the service. For curl you will need to escape any double quotes with a backslash (\").
The /status/alive and /status/ready currently return OK on the same conditions.
TODOs: