Skip to content

The Azure DevOps extension for PowerOn Pipelines has two tasks ValidatePowerOn and SynchronizeDirectory. For GitHub, these are split into two individual actions and can be referenced as such in your GitHub repository designated for Symitar.

Validate PowerOn

This GitHub action will validate the PowerOns which flux in either a PR or a merge into one of your branches. To learn more about it, check it out here: https://github.com/marketplace/actions/validate-poweron

In v2.2, validation uses the Symitar connector over SSH. Legacy connection inputs are accepted but ignored; non-PR comparisons use SFTP checksums. YAML-list inputs and preserve-server-files remain supported. Earlier releases retain their older connection behavior.

Synchronize Symitar

This GitHub action will synchronize your PowerOn files, DataFiles, LetterFiles, or HelpFiles in a very configurable way. Choose to pull remote files, push local ones, or mirror the Symitar directory with yours. To learn more about it, check it out here: https://github.com/libum-llc/synchronize-symitar-action

Recent versions also support server-managed file preservation with preserve-server-files, pull-preserved-only workflows, SFTP concurrency, direct commits for pulled changes, and pull-request based review flows for protected branches.

The planned v2.2 synchronization action adds byte verification, read-only dry runs, preservation exclusions, and opt-in reinstall-dependent-powerons with a files-reinstalled output. GitHub inputs use kebab-case; Azure DevOps task inputs use camelCase. See the migration guide before adopting these options.