Home
Extending Product Function
Learn how to extend the function of HCL DevOps Deploy (Deploy).
REST API reference
You can use these REST interfaces to automate tasks.
REST commands for the DevOps Deploy server
The following list shows the commands that are available for the HCL DevOps Deploy (Deploy) server.
serverKeystore resource
Complete a server keystore import task
Complete a server keystore import task by uploading a keystore containing new key pairs. The uploaded keystore must be in a format consumable by your Java virtual machine; currently, JKS and PKCS12 are the supported formats. Your Java virtual machine may impose additional restrictions such that keystores from other virtual machines or generated by other tools may not be readable. Imports can only be completed by the same user that created the import task.

Extending Product Function
Learn how to extend the function of HCL DevOps Deploy (Deploy).
- Plug-ins
  The HCL plug-ins provide tools for creating component processes and integrations. HCL plug-ins provides plug-ins for several common deployment processes, and others are available to integrate with a wide variety of tools, such as middleware tools, databases, and servers.
- Creating notification templates
  Notification templates are the basis for emails that the server sends to users after an event occurs on the server. You can create customized notification templates by modifying the default templates provided, or by creating new templates of your own.
- REST API reference
  You can use these REST interfaces to automate tasks.
  - Running REST commands
    Many different programs can run REST commands. To run the command, you call a method on a REST resource and pass parameters or a request in JSON format.
  - Examples of REST API commands
    Many REST and command-line client commands have examples in their help topics. A few more examples using various programming languages and scenarios are provided here. The commands are similar for the server.
  - Authenticating for REST commands
    The way that you authenticate to run REST commands depends on how the server is set up and the tool that you are using to run the commands.
  - REST commands for the DevOps Deploy server
    The following list shows the commands that are available for the HCL DevOps Deploy (Deploy) server.
    - agentCLI resource
      Resources for creating, editing, and deleting agents.
    - agentPool resource
    - application resource
      Resources for working with applications, including manipulating the components and environments that are associated with applications.
    - applicationPipeline resource
    - applicationProcess resource
    - applicationProcessRequest resource
      Resources for requesting application processes.
    - applicationTemplate resource
      Resources for working with application templates.
    - approval/task resource
      Resources for creating, editing, and deleting agents.
    - authenticationRealm resource
    - blueprint resource
    - calendar resource
    - component resource
    - componentProcess resource
      Resources for working with component processes.
    - componentProcessRequest resource
    - componentTemplate resource
    - deploymentTrigger resource
    - diagnostics/latency resource
    - environment resource
    - environmentTemplate resource
    - frontendServer resource
    - group resource
    - inventory resource
    - javaPackage resource
    - license resource
    - login resource
    - postProcessingScript resource
    - process resource
      Resources for editing and creating generic processes.
    - processRequest resource
    - relay resource
    - resource resource
    - resourceTemplate resource
      Resource for working with resource templates.
    - secretstore resource
    - serverKeystore resource
      - Cancel an incomplete keystore import task
        Incomplete tasks can be cancelled by any user with the required permission.
      - Complete a server keystore import task
        Complete a server keystore import task by uploading a keystore containing new key pairs. The uploaded keystore must be in a format consumable by your Java virtual machine; currently, JKS and PKCS12 are the supported formats. Your Java virtual machine may impose additional restrictions such that keystores from other virtual machines or generated by other tools may not be readable. Imports can only be completed by the same user that created the import task.
      - Delete a server keystore entry
        A 409 Conflict status is returned if the alias longer corresponds to the same certificate at the time of the request. If the alias was never present or was removed concurrently, this operation reports success.
      - Get an existing keystore import task
      - Get information about the server keystore
        The server keystore stores keypairs and certificates used for agent communication.
      - Prepare for importing server keystore key pair entries
        Prepare for importing server keystore key pair entries by creating a new import task.
    - snapshot resource
    - sshInstallAgent resource
    - status resource
    - systemConfiguration resource
    - tags resource
      Resources for listing tags.
    - team resource
    - teamsecurity resource
    - user resource
    - vault/appRole resource
    - version resource
    - webhookTemplate resource
    - workflowTrace resource
    - zInventory resource
      Resources for manipulating Z inventory.
- Command-line client (CLI) reference
  CLI is a command-line interface that provides access to the HCL DevOps Deploy (Deploy) server. It can be used to find or set properties and to run numerous functions.
- Process-as-code feature
  Programmatically manage processes with PAC language.

Complete a server keystore import task

Complete a server keystore import task by uploading a keystore containing new key pairs. The uploaded keystore must be in a format consumable by your Java virtual machine; currently, JKS and PKCS12 are the supported formats. Your Java virtual machine may impose additional restrictions such that keystores from other virtual machines or generated by other tools may not be readable. Imports can only be completed by the same user that created the import task.

Request

POST https://{hostname}:{port}
    /cli/serverKeystore/completeImportTask?{parameters}
Accept: {contentType}
Content-Type: application/octet-stream

Table 1. Request parameters
Parameter	Type	Required	Description
task	string	true	ID of a prepared import task to complete

Table 2. Header parameters
Parameter	Type	Required	Description
Content-Type	`application/octet-stream`	true
Accept	`application/json` `application/yaml`	true

Related CLI command: completeServerKeystoreImportTask.