Skip to content

The PowerOn Pipelines Azure DevOps extension comes with two primary tasks which can be configured to best serve your credit union. This page gives a comprehensive overview of what's available within each one.

SynchronizeDirectory

Available • Synchronizes a Symitar directory (DATAFILES, LETTERSPECS, HELPFILES, or REPWRITERSPECS) with your Azure DevOps repository using a release artifact created as your default branch receives changes. In the case of PowerOn files (e.g. the REPWRITERSPECS directory), the task will Install & Uninstall based on your checked-in PowerOn Pipelines configuration.

Inputs

The following inputs are available using the SynchronizeDirectory task in any Azure DevOps pipeline.

Directory Type

directoryType • Selects the Symitar directory targeted by synchronization.

  • dataFiles - targets the DATAFILES directory on your target Sym
  • helpFiles - targets the HELPFILES directory on your target Sym
  • letterFiles - targets the LETTERSPECS directory on your target Sym
  • powerOns - targets the REPWRITERSPECS directory on your target Sym
Required Available Values Default Value
Yes dataFiles, helpFiles, letterFiles, powerOns powerOns

Local Directory Path

localDirectoryPath • This is the local directory path in your repository containing the files to synchronize. It is relative to the extracted artifact root and the defaults listed below are dependent on your value for directoryType.

Required Available Values Default Value
No --
  • DATAFILES/ with dataFiles
  • HELPFILES/ with helpFiles
  • LETTERSPECS/ with letterFiles
  • REPWRITERSPECS/ with powerOns

Connection Type

connectionType • Deprecated; no-op in v2.2. In v2.2, both tasks use the Symitar connector over SSH. Omitted, blank, legacy, and other values all use the same connector. Retaining the input keeps existing YAML valid; it does not select a transport or trigger connector fallback. Remove it from new configurations.

Required Accepted Values Default Value
No Any string; ignored quest

Sync Mode

syncMode • This determines how to synchronize your Sym directory relative to your local path.

  • push - uploads new or byte-different local files; does not delete server-only files
  • pull - downloads new or byte-different server files; never installs PowerOns
  • mirror - makes the selected server scope match the local directory, including deletions, while preserving excluded files
Required Available Values Default Value
Yes push, pull or mirror --

Dry Run

isDryRun • This determines whether or not to make physical changes in the Sym. With this enabled no files are changed, only output which will communicate what would have changed.

Required Available Values Default Value
Yes true or false true

Skip PowerOn Validation

skipValidation • Skip standalone validation of changed PowerOns during push/mirror. Defaults to false. It does not skip compilation or installation health checks when a PowerOn is installed. Ignored for pull and other directory types.

Reinstall Dependent PowerOns

reinstallDependentPowerOns • New in v2.2; defaults to false. During PowerOn push/mirror, trace direct and nested #INCLUDE relationships and install affected parents from installPowerOns, even when the parent's source is unchanged. Preserved parents are excluded. Dry runs list each parent once with its dependency chain and identify whether it needs an installation or reinstallation without a source upload.

Requires each eligible parent's complete source tree in the artifact. Missing or ambiguous filenames, cycles, still-referenced deleted includes, and divergent preserved dependencies fail before deployment. See dependent reinstall behavior.

Sync Method

syncMethod • The transport method for file synchronization. SFTP is the default and supports concurrent transfers. Optional rsync requires rsync and sshpass on the agent; Windows also requires working WSL with Bash and setsid under the agent service account. Both methods use SFTP for checksum planning, snapshots, and verification. A dry run does not execute rsync or verify that its dependencies work. See agent prerequisites.

Required Available Values Default Value
No rsync or sftp sftp

SFTP Concurrency

sftpConcurrency • Number of concurrent SFTP transfers (1-20). Only applies when syncMethod is set to sftp.

Required Available Values Default Value
No 1 through 20 4

Preserve Server Files

preserveServerFiles • Comma-delimited list of exact filenames or glob patterns where the Symitar copy should be preserved during push and mirror. Use with pullPreservedOnly to pull only these files from Symitar. When omitted or empty, the task uses the preserveServerFiles array from .poweron-pipelines/config.yml. Patterns are evaluated in order; prefix a later pattern with ! to re-include files, such as RD.*,!RD.CUSTOM.PO.

Required Available Values Default Value
No -- Config value or empty

Pull Preserved Only

pullPreservedOnly • When syncMode is pull, only download files matched by preserveServerFiles. If no preserve patterns are configured, the task exits without pulling files.

Required Available Values Default Value
No true or false false

Commit Pulled Changes

commitPulledChanges • When syncMode is pull, commit and push pulled repository changes directly after synchronization. The task never commits during a dry run. Prefer createPullRequest when branch policies protect the target branch.

Required Available Values Default Value
No true or false false

Create Pull Request

createPullRequest • When syncMode is pull, commit pulled changes to a separate branch and create or reuse an Azure Repos pull request. The pipeline checkout must use persistCredentials: true for the Git push, and the build service identity needs permission to contribute to the source branch and create pull requests.

Required Available Values Default Value
No true or false false

Commit Message

commitMessage • Commit message used when commitPulledChanges or createPullRequest is enabled.

Required Available Values Default Value
No -- chore: sync server-managed Symitar files [skip ci]

Commit Branch

commitBranch • Branch to push the commit to when commitPulledChanges is enabled. Defaults to the checked-out branch.

Required Available Values Default Value
No -- Checked-out branch

Pull Request Branch

pullRequestBranch • Source branch used for generated pull requests. A fixed branch name updates the same pull request on later runs.

Required Available Values Default Value
No -- chore/symitar-pull

Pull Request Target Branch

pullRequestTargetBranch • Target branch for generated pull requests. Defaults to the build source branch name.

Required Available Values Default Value
No -- Build source branch

Pull Request Title

pullRequestTitle • Title for the generated pull request.

Required Available Values Default Value
No -- chore: sync server-managed Symitar files

Pull Request Description

pullRequestDescription • Description for the generated pull request.

Required Available Values Default Value
No -- Auto-generated pull of server-managed Symitar files.

Git User Name

gitUserName • Git author name used when commitPulledChanges or createPullRequest is enabled.

Required Available Values Default Value
No -- libum-bot

Git User Email

gitUserEmail • Git author email used when commitPulledChanges or createPullRequest is enabled.

Required Available Values Default Value
No -- bot@libum.io

Repository Path

repositoryPath • Path to the Git checkout used when commitPulledChanges or createPullRequest is enabled. Defaults to BUILD_SOURCESDIRECTORY.

Required Available Values Default Value
No -- BUILD_SOURCESDIRECTORY

Azure DevOps Access Token

azureDevOpsAccessToken • Token used for the Azure Repos pull request API. Required for PR creation; defaults to System.AccessToken when available. The Git push still requires checkout: self with persistCredentials: true.

Required Available Values Default Value
No -- System.AccessToken

Artifact Path

artifactPath • Path to the extracted repository, relative to $(System.ArtifactsDirectory). For example, extract to $(System.ArtifactsDirectory)/repo and set artifactPath: repo. Keep .poweron-pipelines/config.yml inside that repository root.

Required Available Values Example Value
Yes -- repo

Symitar Hostname

symitarHostname • The endpoint by which you connect to the Symitar host.

Required Available Values Example Value
Yes -- symitar.example.com

Symitar App Port

symitarAppPort • Deprecated; no-op in v2.2. Accepted for existing YAML but neither required, parsed, nor validated. The v2.2 transport does not use the Symitar Application Server port. Configure the active sshPort instead; do not copy the old application port into it.

Required Accepted Values Default Value
No Existing value; ignored None

SSH Username

sshUsername • The AIX user name for the Symitar host.

Required Available Values Example Value
Yes -- libum

SSH Password

sshPassword • The AIX password for the Symitar host.

Required Available Values Example Value
Yes -- $(sshPassword)

SSH Port

sshPort • The port to connect to the Symitar (AIX) host over SSH.

Required Available Values Default Value
No -- 22

Approved SSH Host Public Key

sshHostKey • The base64 public-key field of an administrator-approved SSH host key. This is not a private key, SHA256 fingerprint, or entire known_hosts line. If omitted, the task reads the agent account's ~/.ssh/known_hosts using ssh-keygen.

Unknown or changed keys fail the task before credentials are sent. The agent never prompts for yes, accepts a new key automatically, or writes to known_hosts. Supply sshHostKey: $(sshHostKey) from a shared variable group for unattended agents. See host trust setup.

Required Accepted Values Default Value
When the agent has no matching trusted key Approved public key's base64 field Agent account's known_hosts

Symitar User Number

symitarUserNumber • Your Symitar user number (fka. Teller Number). It is recommended you provide more of a "system user" instead of your personal for Production instances.

Required Available Values Example Value
Yes -- 1995

Symitar User Password

symitarUserPassword • Your Symitar user password.

Required Available Values Example Value
Yes -- $(symitarUserPassword)

API Key

apiKey • Your PowerOn Pipelines API Key from Libum Portal.

Required Available Values Default Value
Yes See API Keys in Libum Portal --

Sym Number

symNumber • The directory (aka Sym) number to deploy to. If nothing is defined here, the task will attempt to pull from the branchSymNumbers you have defined in your Configuration.

Required Available Values Example Value
No -- 627

Debug

debug • Enable debug logging for the Symitar client.

Required Available Values Default Value
No true or false false

Outputs

Name the step (for example, name: sync) to read outputs as $(sync.filesDeployed) in later steps. Successful dry runs publish proposed counts; an actual run publishes counts only after verification succeeds.

Output Meaning
filesDeployed Files uploaded or downloaded
filesDeleted Files removed
filesInstalled All PowerOn installation operations, including dependent reinstalls
filesReinstalled Unchanged, previously installed parents reinstalled because an include changed; included in filesInstalled
filesUninstalled PowerOns uninstalled
outliersCount Server drift excluded by a preserved-only pull
outlierFiles JSON array of those outlier filenames
pullRequestId Created or reused Azure Repos PR ID, when applicable
pullRequestUrl Created or reused PR URL, when applicable

Installation counts are zero for pull and for non-PowerOn directories. See synchronization guarantees and limits.

ValidatePowerOn

Available • Validates the updated PowerOn files in the configured powerOnsDirectory. In the PR context this will only validate changes between target and source branches. In the build context, this will validate differences between the current state and what exists in the provided symNumber.

Inputs

The following inputs are available using the ValidatePowerOn task in any Azure DevOps pipeline.

Connection Type

connectionType • Deprecated; no-op in v2.2. In v2.2, both tasks use the Symitar connector over SSH. Omitted, blank, legacy, and other values all use the same connector. Retaining the input keeps existing YAML valid; it does not select a transport or trigger connector fallback. Remove it from new configurations.

Required Accepted Values Default Value
No Any string; ignored quest

Symitar Hostname

symitarHostname • The endpoint by which you connect to the Symitar host.

Required Available Values Example Value
Yes -- symitar.example.com

Symitar App Port

symitarAppPort • Deprecated; no-op in v2.2. Accepted for existing YAML but neither required, parsed, nor validated. The v2.2 transport does not use the Symitar Application Server port. Configure the active sshPort instead; do not copy the old application port into it.

Required Accepted Values Default Value
No Existing value; ignored None

SSH Username

sshUsername • The AIX user name for the Symitar host.

Required Available Values Example Value
Yes -- libum

SSH Password

sshPassword • The AIX password for the Symitar host.

Required Available Values Example Value
Yes -- $(sshPassword)

SSH Port

sshPort • The port to connect to the Symitar (AIX) host over SSH.

Required Available Values Default Value
No -- 22

Approved SSH Host Public Key

sshHostKey • The base64 public-key field of an administrator-approved SSH host key. This is not a private key, SHA256 fingerprint, or entire known_hosts line. If omitted, the task reads the agent account's ~/.ssh/known_hosts using ssh-keygen.

Unknown or changed keys fail the task before credentials are sent. The agent never prompts for yes, accepts a new key automatically, or writes to known_hosts. Supply sshHostKey: $(sshHostKey) from a shared variable group for unattended agents. See host trust setup.

Required Accepted Values Default Value
When the agent has no matching trusted key Approved public key's base64 field Agent account's known_hosts

Symitar User Number

symitarUserNumber • Your Symitar user number (fka. Teller Number). It is recommended you provide more of a "system user" instead of your personal for Production instances.

Required Available Values Example Value
Yes -- 1995

Symitar User Password

symitarUserPassword • Your Symitar user password.

Required Available Values Example Value
Yes -- $(symitarUserPassword)

API Key

apiKey • Your PowerOn Pipelines API Key from Libum Portal.

Required Available Values Default Value
Yes See API Keys in Libum Portal --

Sym Number

symNumber • The directory (aka Sym) number to deploy to. If nothing is defined here, the task will attempt to pull from the branchSymNumbers you have defined in your Configuration.

Required Available Values Example Value
No -- 627

PowerOns Directory

powerOnsDirectory • The directory in the repository to monitor PowerOn changes in.

Required Available Values Default Value
No -- REPWRITERSPECS/

Preserve Server Files

preserveServerFiles • Comma-delimited list of exact filenames or glob patterns to skip during validation because the Symitar copy is preserved. When omitted or empty, the task uses the preserveServerFiles array from .poweron-pipelines/config.yml. Patterns are evaluated in order; prefix a later pattern with ! to re-include files, such as RD.*,!RD.CUSTOM.PO.

Required Available Values Default Value
No -- Config value or empty

Sync Method

syncMethod • Compatibility-only in ValidatePowerOn v2.2; it does not select the comparison transport. Accepted values remain sftp and rsync (default sftp), but non-PR validation always uses SFTP checksum comparisons. PR validation selects changes from Git. Invalid values still fail input validation, so this is not an arbitrary-value no-op like connectionType.

SynchronizeDirectory.syncMethod remains an active SFTP/rsync transfer choice.

Debug

debug • Enable debug logging for the Symitar client.

Required Available Values Default Value
No true or false false

Outputs

Name the step (for example, name: validate) to reference these outputs in later steps. Inspect filesFailed together with the task result; a zero-file selection is a successful no-op.

Output Meaning
filesValidated Selected PowerOns validated
filesPassed Selected PowerOns that passed
filesFailed Selected PowerOns that failed validation