Deployment spaces

A deployment space is a logical container that includes a set of decision service archives and their associated metadata. Each deployment space can store different custom metadata for the same decision service archive.

You can use these deployment spaces to support a promotion workflow through different stages of the software development lifecycle.

Decision service archives are initially deployed to a target deployment space. If you are using the decision runtime REST API, you can deploy them to any deployment space of your choice. If you are using Decision Designer, the decision service archive is deployed to the embedded deployment space by default.

You can then promote the deployed decision service archive to another deployment space either by using a dedicated endpoint of the decision runtime REST API.

You can promote a decision service archive from any deployment space to any other deployment space.

Endpoint for promotion:

/deploymentSpaces/{sourceDeploymentSpaceId}/decisions/{decisionId}/promote

Parameters:

  • sourceDeploymentSpaceId is the source deployment space for the decision service archive to promote.
  • decisionId is the identifier of the decision service archive to be promoted.

Specify the information about the target deployment space ID in the request body.

For example:
{
    "targetDeploymentSpaceId": "production"
}

For more information about how to use the endpoint, see the OpenAPI description for the decision runtime REST API in Reference.

When you promote a decision service archive, the archive and its metadata are copied to the target deployment space. A new promotionTime metadata is added to record when the promotion occurred.