Not compatible with latest filemapper module

[alexjfisher]

This module appears not to work correctly with the latest filemapper releases (now maintained by the Vox Pupuli project). It is not idempotent and doesn't preserve non-managed parts of the yaml file.

eg

[root@localhost ~]# cat test.yml
transports:
  rest.agent.transport:
    enabled: false
  websocket.transport:
    consoleUri: wss://mule-manager.anypoint.mulesoft.com:443/mule
    handshake:
      enabled: true
      body: null
globalConfiguration:
  security:
    keyStoreAlias: agent
  authenticationProxy:
    endpoint: https://arm-auth-proxy.prod.cloudhub.io
  proxyConfiguration:
    host: 1.1.1.1
    port: '3128'
internalHandlers:
  mule.agent.tracking.handler.analytics:
    enabled: false
[root@localhost ~]# cat test.pp
yaml_setting { 'mule agent proxy host':
      target  => '/root/test.yml',
      key     => 'globalConfiguration/proxyConfiguration/host',
      value   => 'host.example.com',
}
[root@localhost ~]# puppet apply --modulepath=/root/modules test.pp
Notice: Compiled catalog for localhost in environment production in 0.09 seconds
Notice: /Stage[main]/Main/Yaml_setting[mule agent proxy host]/ensure: created
Notice: Applied catalog in 0.11 seconds
[root@localhost ~]# cat test.yml
---
globalConfiguration:
  proxyConfiguration:
    host: host.example.com

[root@localhost ~]#

If I use adrien/filemapper, everything works fine.

I've been able to work out it was voxpupuli/puppet-filemapper#10 that broke this module, but have no idea how to fix it! Any ideas? Thanks.

[dploeger]

Same here. I tried to fundle with passages in the code handling :nil, but not successful. @reidmv Could you perhaps shine some light on this? I moved to adrien/filemapper now, as well, although this is not maintained anymore.