| Anchor | ||||
|---|---|---|---|---|
|
...
Attributes | Type | Description |
|---|---|---|
| description | String | Description of the Instance |
| environments | List<Long> | List of the Environment Ids that are associated with this instance |
| workflows | List<Long> | List of the workflow ids that are associated with this instance |
| instanceId | String | The unique id of the instance. The id is made when making the instance, and it is returned in the JSON. |
| instanceName | String | Name of the instance |
| isActive | Boolean | Whether or not this instance is active. |
| plugins | List<Plugin> | List of the plugins that are associated with this instance |
| instanceCode | String | The code of the Instance |
| groupCode | String | The group code of the instance |
| subGroupCode | String | The sub group code of the instance |
| isDeploymentTarget | Boolean | Whether or not this instance is a deployment target. |
Since plugins can have multiple operations, a plugin id is not enough to determine which plugin is desired. To designate a plugin, both an owner id and property set name must be includedA plugin operation, relative to an instance, is defined by the following two fields.
| Attributes | Type | Description |
|---|---|---|
| ownerId | Long | The id of the desired plugin |
| propertySetName | String | The name of the desired plugin operation |
...
Parameters
Parameter | Required | Type | Description |
|---|---|---|---|
| Id | Yes | URL | URL parameter for the Id which is used to find and return an instance |
Response Codes
HTTP Code | Description |
|---|---|
| 200 | Instance was found and returned |
| 400 | Bad request |
| 401 | Unauthorized |
| 500 | Unexpected internal server error |
Example
If we had an Instance in our database with an Id of 11004 with the following attributes
| Code Block | ||||
|---|---|---|---|---|
| ||||
{
"description": "GET example description",
"environments": [11001],
"workflows": [],
"instanceId": 11004,
"instanceName": "GET Example Name",
"isActive": true, "plugins": [],
"instanceCode": "GETEXAMPLECODE",
"groupCode": "GET example group",
"subGroupCode": "GET example sub group",
"isDeploymentTarget": false
} |
When we run a GET request at the following URL
http://host:port/flexdeploy/rest/topology/instance/11004
The GET request would return the following JSON Instance object
| Code Block | ||||
|---|---|---|---|---|
| ||||
{
"description": "GET example description",
"environments": [11001],
"workflows": [],
"instanceId": 11004,
"instanceName": "GET Example Name",
"isActive": true, "plugins": [],
"instanceCode": "GETEXAMPLECODE",
"groupCode": "GET example group",
"subGroupCode": "GET example sub group",
"isDeploymentTarget": false
} |
GET by Query Parameters
This GET service will return a list of Instances in the form of JSON objects based on the query parameters instanceCode, instanceName, groupCode, and subGroupCode. Instances are only returned if they match ALL of the specified query parameters. If no query parameters are given this request will return the entire list of Instances. The instanceName parameter returns instances that contain the specified parameter. The other parameters must be equal to the instance.
| Info | ||
|---|---|---|
| ||
http://host:port/flexdeploy/rest/topology/instance? Append the following character sequences to the above URL to specify Query parameters.Use '&' between successive query parameters:instanceCode={instanceCode} instanceName={instanceName} groupCode={groupCode} subGroupCode={subGroupCode} Examples:To Specify the code parameter only:http://host:port/flexdeploy/rest/topology/instance?instanceCode={instanceCode} To Specify the code and group code parameters:http://host:port/flexdeploy/rest/topology/instance?instanceCode={instanceCode}&groupCode={groupCode} To Specify the name, group code, and sub group code parameters:http://host:port/flexdeploy/rest/topology/instance?instanceName={instanceName}&groupCode={groupCode}&subGroupCode={subGroupCode} |
...