Home
Extending Product Function
Learn how to extend the function of HCL DevOps Deploy (Deploy).
Process-as-code feature
Programmatically manage processes with PAC language.
Application process steps
Lists the various application steps that can be used in a process.
join
The join application process step.

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.
- 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.
  - Using the PAC commands
    Use the PAC language to create HCL DevOps Deploy (Deploy) processes.
  - Understanding the PAC file format
  - Application process steps
    Lists the various application steps that can be used in a process.
    - application-run-component-process
      The application-run-component-process step executes a component process and waits for it to complete. This step is only valid in an application process.
    - apply-configuration
      The apply-configuration step starts child component processes for applying configuration changes. This step is only valid in an application process.
    - for-each-agent
      The for-each-agent application process step lets you run a process for each agent in an environment.
    - for-each-resource-tag
      The for-each-resource-tag application process step lets you run processes for resources selected by tag. This step is only valid in an application process.
    - install-component
      The install-component application process step starts child component processes that install a single component. This step is only valid in an application process.
    - install-multiple-components
      The install-multiple-components step runs child component processes that install multiple components. This step is only valid in an application process.
    - join
      The join application process step.
    - release-lock
      The release-lock step releases a process lock.
    - rollback-component
      The rollback-component step starts child component processes for rolling back a single component. This step is only valid in an application process.
    - rollback-multiple-components
      The rollback-multiple-components step starts child component processes for rolling back multiple components. This step is only valid in an application process.
    - run-operational-process-for-multiple-components
      The run-operational-process-for-multiple-components step executes a component operational process for multiple components and waits for them to complete. This step is only valid in an application process.
    - uninstall-component
      The uninstall-component step starts child component processes for uninstalling a single component. This step is only valid in an application process.
    - uninstall-multiple-components
      The uninstall-multiple-components step starts child component processes for uninstalling multiple components. This step is only valid in an application process.
  - Core component process steps
    Lists the various core component steps that can be used in a process.
  - Generic process steps
    Lists the various generic steps that can be used in a process.

join

The join application process step.

Format

The join step halts processing until all connected steps are completed. The only valid completion condition is success, so on success is not required or permitted.

This step does not have properties.

Example

join step "foo" is
    finish
end