[dev.icinga.com #14031] Workaround for PuppetDB

[icinga-migration]

This issue has been migrated from Redmine: https://dev.icinga.com/issues/14031

Created by dgoetz on 2017-01-16 12:55:55 +00:00

Assignee: lbetz
Status: New
Target Version: (none)
Last Update: 2017-01-16 13:09:54 +00:00 (in Redmine)

---

I was hit by an ugly bug of PuppetDB: https://tickets.puppetlabs.com/browse/PDB-170
It effects exported resources containing arrays of only one element which will be stored as string and so collected. At least version 2.3 (required by Puppet 3.7) is affected, I hope newer versions work as I am the first one hit by this.
In the case of this module it hits primarily endpoints array of zone objects.

[icinga-migration]

Updated by lbetz on 2017-01-16 12:57:24 +00:00

• Assigned to set to lbetz

[icinga-migration]

Updated by lbetz on 2017-01-16 13:09:54 +00:00

• Done % changed from 0 to 10

modify of define resource 'zone' for tests.

[dgoetz]

I now managed to get verification that this workaround works fine. Thanks! 👍

[kwisatz]

Isn't this a duplicate of #152, e.g. the Array/String thing?

[lbetz]

finished 100%
can be merged