Configuration | Libum Docs

We've extended the use of Tasks in PowerOn Pipelines to consider a defined configuration which is present in the repository. With this, you'll be able to define things like which PowerOns should be installed during deployments, and even what branch maps to which Sym number.

Creating the config file⁠

In your Symitar repository, create a config.yml under a folder named .poweron-pipelines. The following example defines a global powerOnsDirectory input and sets the main branch to deploy and validate using Sym 627.

# Default inputs that apply to all tasks
inputs:
  powerOnsDirectory: REPWRITERSPECS/

# Map of branch / symNumber relationships
branchSymNumbers:
  main: 627

This will be considered by every Task within PowerOn Pipelines and the ingested values will be printed in the logs so your always aware of what values are being used where.

Available configurations⁠

The following are the available options for the configuration file.

inputs.powerOnsDirectory⁠

Sets the powerOnsDirectory (which is the location of your local PowerOns) for every PowerOn Pipelines Task in the repository. This will be overwritten by individual task configurations if they explicitly set this input.

# Example: Default powerOnsDirectory which applies to all tasks
inputs:
  powerOnsDirectory: REPWRITERSPECS/

inputs.letterFilesDirectory⁠

Sets the letterFilesDirectory (which is the location of your local LetterFiles) for every PowerOn Pipelines Task in the repository. This will be overwritten by individual task configurations if they explicitly set this input.

# Example: Default letterFilesDirectory which applies to all tasks
inputs:
  letterFilesDirectory: LETTERSPECS/

inputs.dataFilesDirectory⁠

Sets the dataFilesDirectory (which is the location of your local DataFiles) for every PowerOn Pipelines Task in the repository. This will be overwritten by individual task configurations if they explicitly set this input.

# Example: Default dataFilesDirectory which applies to all tasks
inputs:
  dataFilesDirectory: DATAFILES/

inputs.helpFilesDirectory⁠

Sets the helpFilesDirectory (which is the location of your local HelpFiles) for every PowerOn Pipelines Task in the repository. This will be overwritten by individual task configurations if they explicitly set this input.

# Example: Default helpFilesDirectory which applies to all tasks
inputs:
  helpFilesDirectory: HELPFILES/

branchSymNumbers⁠

Map of Symitar repository branches to their symNumber.

# Example: Map of branch / symNumber relationships
branchSymNumbers:
  main: 627

installPowerOns⁠

List of PowerOn files which should be installed during deployments & uninstalled if removed.

# Example: List of PowerOn files to install
installPowerOns:
  - LB.VALID.PO

validateIgnorePowerOns⁠

List of PowerOn files which should be ignored at any point where validation is performed.

# Example: Skip ASCII files in the PowerOn directory (which will always fail)
validateIgnorePowerOns:
  - ASCIICHAR.DATA
  - RB.SYNERGY.AP.INDEX.ASCIIDATA

preserveServerFiles⁠

List of exact filenames or glob patterns where Symitar should remain the source of truth. Matched files are skipped during validation, preserved during push and mirror synchronization, and can be pulled back from Symitar with the pullPreservedOnly workflow.

# Example: Preserve files generated or forcibly updated by Symitar
preserveServerFiles:
  - RD.*
  - PFR.*

Configuration⁠