Scap3 reads in configuration variable values from YAMLs, either from vars.yaml or from the Puppet-compiled file located on the host, and puts them into Python dict()s. On the output side, however, they are forced into strings regardless of the output format used by the actual configuration file, which may result in unexpected values, such as proxy: None instead of proxy: or enableFeature: True instead of enableFeature: true.

A way around this would be to have different output processors which can be specified in config-files.yaml:

/etc/service/config.yaml:
  template: config.yaml.j2
  erb_syntax: True
  output_format: yaml

Then, Scap2 could process all non-string values and turn them into appropriate, valid YAML values (in this example). This would also allow us later expand processing to other configuration-file formats.