[MXS-1220] REST API Created: 2017-04-14  Updated: 2017-08-09  Resolved: 2017-06-14

Status: Closed
Project: MariaDB MaxScale
Component/s: Core
Affects Version/s: None
Fix Version/s: 2.2.0

Type: New Feature Priority: Major
Reporter: markus makela Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: None

Sub-Tasks:
Key
Summary
Type
Status
Assignee
MXS-1229 Add POST/PUT/PATCH support Sub-Task Closed markus makela  
MXS-1236 Add tests for REST API Sub-Task Closed markus makela  
MXS-1252 Implement core diagnostic output Sub-Task Closed markus makela  
MXS-1253 Update REST API resource documentation Sub-Task Closed markus makela  
MXS-1254 Add common request parameters Sub-Task Closed markus makela  
Sprint: 2017-32, 2017-33, 2017-34, 2017-35

 Description   

REST API for Managing MaxScale

Overview

The REST API in MaxScale should be implement as a HTTP based administrative interface that manages resources in MaxScale in a stateless (i.e. RESTful) manner. This allows transactional communication with MaxScale.

Requirements

The API should implement the API documented in the MaxScale REST API documentation.

Implementation details

The current resources closely follow the maxadmin output of the previous versions.

Currently, all object references, e.g. servers in services, are expressed as relative pathnames. This means that nested resources in services, filters and monitors need to be queried separately. The required linkage of the nested resources could be done inside MaxScale so that only one query is needed to fully display an object.

The layout of the resources follow the JSON API specification: http://jsonapi.org/


Generated at Thu Feb 08 04:05:06 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.