ZAPP Configuration Property Store

IBM® Enterprise Edition for Galasa supports using a zapp.yaml file as the Galasa Configuration Property Store (CPS). This is for properties that would otherwise be stored in the cps.properties file.

framework.extra.bundles=com.ibm.galasa.framework framework.config.store=zapp:[path/to/zapp.yaml/file]

Note that the path does not include the file name, which is always zapp.yaml.

Within a zapp.yaml file, Galasa configuration properties are specified in the settings object of a profile with type galasa. ZAPP properties are converted to Galasa properties by concatenating all of the keys with a period (.) separator and replacing camel-cased keys with each word lower-cased and separated by periods. If a tag key is specified, its corresponding value is inserted into the property name at that point. Galasa properties that are not supported by the ZAPP schema can be specified under additionalProperties as a name/value pair.

For example:

profiles:
  - name: galasa_properties_for_functional_test
    type: galasa
    settings:
      zos:
        dseTags:
          - tag: PRIMARY
            imageid: MVS1
        images:
          - tag: MVS1
            ipv4Hostname: mvs1.example.com
            telnet:
              port: 1234
            credentials: USER1
      additionalProperties:
        - name: zos.cluster.DEFAULT.images
          value: MVS1

is equivalent to the following in a cps.properties file:

zos.dse.tags.PRIMARY.imageid=MVS1
zos.images.MVS1.ipv4.hostname=mvs1.example.com
zos.images.MVS1.telnet.port=1234
zos.images.MVS1.credentials=USER1
zos.cluster.DEFAULT.images=MVS1