Infrastructure Management

The Infrastructure Management API endpoints can query, create, and update servers, environments, and server roles; they are designed to automate the setup and management of a BuildMaster instance.

API Key Usage

All of these endpoints require that an API key with Infrastructure Management access is passed into each request. The examples use a query string for simplicity, but you can also use a header, a form value, or a JSON property. For more information, see API Access and API Keys for more information.

Data Specification

This endpoint sends and receives entries as JSON objects.

Server

Server Role

Environment

Endpoint Specifications

All of the infrastructure management endpoints follow the same convention:

POST /api/infrastructure/«entry-type»/«action-type»/«entry-name»?key=«api-key»

• entry-type is one of servers, roles, or environments
• action-type is one of [list](#list), [create](#create), [update](#update), or [delete](#delete)
• entry-name is the name of the entry being created, updated, or deleted; it is not valid on a list action type

List Entries

This returns a status of 200 (on success), or 403 (api key not authorized), and a body containing only an array of entry objects.

List Servers

POST /api/infrastructure/servers/list?key=secure123

[
  {
    "name": "hdarsintsv1",
    "roles": \["web","hdars"\],
    "environments": \["integration"\],
    ...
    "variables": { 
                   "disk-path": "/var/hdars/1000", 
                   "app-name": "hdars" 
                 },
    "active": true
  },
  {
    "name": "mdapxsv",
    "roles": \[\],
    "environments": \["test1","test2"\],
    ...
    "variables": {}
  },
  { ... }
]

List Server Roles

POST /api/infrastructure/roles/list?key=secure123

[
  {
    "name": "web",
    "variables": { 
                   "websites-root": "c:\\webroots\\"
                 }
  },
  {
    "name": "hdars",
    "variables": {}
  },    
  { ... }
]

List Environments

POST /api/infrastructure/environments/list?key=secure123

[
  {
    "name": "integration",
    "parent": null,
    "variables": { 
                   "database-alias": "intagration"
                 }
  },
  {
    "name": "testing",
    "parent": null,
    "variables": { 
                   "database-alias": "test"
                 }
  },
  {
    "name": "test1",
    "parent": "testing",
    "variables": {}
  },
  {
    "name": "test2",
    "parent": "testing",
    "variables": {}
  },
  { ... }
]

The above is an example, and truncates responses for readability with ellipses; the API key used requires the Infrastructure_View permission.

Create Entry

This returns a status of 201 (on success), 403 (api key not authorized), or 422 (invalid entry), and an body containing either the entry object, or a description of the 422 status.

If the entity references another entity (e.g., in the roles property of a server, or the parent property of environment) and the referenced entity does not exist, an invalid entry (422) will be returned.

We opted not to provide an example, as the request body is simply a JSON object formatted like the list examples. The API key used requires the Infrastructure_Manage permission.

Update Entry

This returns a status of 200 (on success), 403 (api key not authorized), 404 (entry not found), or 422 (invalid entry), and an body containing either the entry object, or a description of the 422 status.

If the entity references another entity (e.g., in the roles property of a server, or the parent property of environment) and the referenced entity does not exist, an invalid entry (422) will be returned.

If there are missing properties on the entity, only the specified properties will be updated.

Update Server

POST /api/infrastructure/servers/update/hdarsintsv1?key=secure123

{
  "roles": \["web","hdars","code-server"\], 
  "encryption": "none"
}

Note that, in this case, the encryptionKey property would be removed on update because the encryption type changed.

Rename Server Role

POST /api/infrastructure/roles/update/hdars?key=secure123

{ "name": "new-hdars"}

Remove Parent Environment

POST /api/infrastructure/environments/update/test1?key=secure123

{ "parent" : null }

Delete Entry

This returns a status of 200 (on success), 403 (api key not authorized), or 404 (entry not found), and an empty body.