Table 5.35. Create or modify service definition
| Method | URI | Description |
|---|---|---|
| PUT | /admin/services/<full_service_name> | Create or modify manifest file. Request data should be a json object If full_service_name is not specified new manifest file will be created. Otherwise existent service definition (manifest file) will be rewritten with the given data. |
Table 5.36. Parameters
| Parameter | Description | Required |
|---|---|---|
| full_service_name | Identifies the type service (corresponds to full_service_name in manifest) | true |
Table 5.37. Error Response Codes
| Code | Description |
|---|---|
| 401 | User is not authorized to access this tenant resources |
| 400 | If specified full_service_name is not equivalent to that parameter in json or there is no json data in request |
Payload
New manifest created in manifests directory. Metadata Service
Example
Here are json that will create new service manifest in Metadata Repository
(json for service update looks the same - all data will be overwritten with the new one).
Note that service_display_name is a required parameter and full_service_name should correspond
tofull_service_name given in URL or skipped.
{
"full_service_name": "new_service",
"service_display_name" : "Test Service",
"version": "0.1"
}
All other parameters will be set to default parameters.
Returns
In case of successful result this call returns a json:
{"result": "success"}
