Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
icinga-migration opened this issue Jan 16, 2017 · 5 comments
Closed

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

icinga-migration opened this issue Jan 16, 2017 · 5 comments
Assignees
Milestone

Comments

@icinga-migration
Copy link

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
Copy link
Author

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

  • Assigned to set to lbetz

@icinga-migration
Copy link
Author

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
Copy link
Contributor

dgoetz commented Jan 17, 2017

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

@kwisatz
Copy link
Contributor

kwisatz commented Jan 17, 2017

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

@lbetz
Copy link
Member

lbetz commented Jan 17, 2017

finished 100%
can be merged

@lbetz lbetz closed this as completed Jan 17, 2017
@bobapple bobapple added this to the v1.0.0 milestone Jan 18, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants