A deployment configuration defines which project or projects you want to publish and bundle into a deployment image, and a deployment image is set of published packages that you can deploy to or remove from a target instance as a set. 

Available as of v8.1, the LogicNets Deployment Manager allows users with assigned privileges to create deployment configurations, build deployment images, and deploy those images to identified instances. The topics in this section walk you through how to add, configure, and deploy builds.

For commercial information about the LogicNets Deployment Manager go to the LogicNets Deployment Manager (LN-WSP-D) Product page here.

Pre-requisite Roles for Using the Deployment Manager

Where the Deployment Manager is included in your build, you will need to set up the following additional roles for the group of users that need access to manage deployments. These are set up in the UserManagement package.

• Group roles as follows:
  • RepositoryAPI: publish-all role
  • RegistryAPI: write role
  • DeploymentManager: admin role
• Workspace roles as follows:
  • [all] shared workspaces: remote read-modify role