PulseUno SCT

Use the PulseUno source configuration type (SCT) to import packages from a OpenText PulseUno vault.

Import packages from PulseUno

The PulseUno source configuration type imports Maven, npm, and Docker package versions from a PulseUno vault as DA component versions.

Maven, npm Each package is imported as a flat directory with files. The folder structure is not preserved.
Docker Each package is imported as an empty version containing only the associated version properties.

Caution: By default, Deployment Automation imports files up to 100 MB. If any file in the package is larger than 100 MB, the import fails. The default threshold is controlled by the artifact.api.size.threshold property in PulseUno.

To import packages from PulseUno:

  1. Create a component and select PulseUno as the Source Config Type (SCT). For details, see Create components.

  2. Specify the PulseUno SCT settings for the component. See PulseUno SCT settings.

  3. After creating the component, set its version properties. See PulseUno SCT version properties.

Back to top

PulseUno SCT settings

The following table describes the settings specific to the PulseUno source configuration type.

For details on how to specify other component settings, see Create components.

Field Description
PulseUno URL

Specify the URL pointing to a package on the PulseUno server.

To get the package's URL, in PulseUno, drill down to the relevant vault, open the package, and copy the URL in the browser, for example:


Username Enter the username for accessing PulseUno.
Password Enter the password for accessing PulseUno.
Allowed version states

Specify which packages can be imported from PulseUno, based on their state:

  • Pending

  • In approval

  • Approved

  • Unapproved

CTRL+click or SHIFT+click to select multiple states. By default, all states are selected.

Import all new versions (Optional) Select this option to import all the package versions missing from Deployment Automation. By default, Deployment Automation imports only the latest version.
Use latest component properties for versions download

(Optional) Select this option if you want Deployment Automation to use the current component properties instead of the properties that are set when the version is created.

Note: Component version properties are always preserved when a version is created.

Back to top

PulseUno SCT version properties

After you create a component and set PulseUno as its source configuration type, you need to add version properties to the component. This enables Deployment Automation to import version information about PulseUno packages.

Depending on the type of PulseUno packages you're importing, add the following version property definitions.

Package type Property name
Maven, npm, Docker PulseUno.timestamp
Maven, npm, Docker PulseUno.sinceDate
Maven, npm, Docker PulseUno.spaceName
Maven, npm, Docker PulseUno.vaultName
Maven, npm, Docker PulseUno.packageName
Maven, npm, Docker PulseUno.downloadURLs
Maven, npm, Docker PulseUno.packageType
Maven, npm, Docker PulseUno.state
Docker only PulseUno.Docker.imageName
Docker only PulseUno.Docker.tag
Docker only PulseUno.Docker.repository
Docker only PulseUno.Docker.vaultURL

To add version property definitions, navigate to Management > Components > [select component] > Properties > Version PropDefs. For each property, enter the property name, accepting the defaults for the remaining options. For details about version properties, see Add or edit component version properties.

Back to top

See also: