Jira (PUP-3235) CPAN provider for package type
Title: Message Title Ben S commented on PUP-3235 Re: CPAN provider for package type There's meltwater/cpan on the Puppet Forge, and to be honest, you're much more likely to see new package provider types created as a module rather than merged into Puppet Core. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1079) Exported resources is exporting to the database with --noop flag
Title: Message Title Jason Antman commented on PUP-1079 Re: Exported resources is exporting to the database with --noop flag Deepak Giridharagopal Yeah, that is a bit of a dilemma. Speaking for myself: Whether or not facts get exported isn't a big deal to me, as that shouldn't affect my actual catalogs. People who are using something like puppetdbquery might feel otherwise, and want to prevent fact updates as well. I can see arguments in favor of 'yes' or 'no' about this, but don't have a strong opinion for my use case. Resources marked as noop... I'm honestly not sure. I'm leaning towards no (it shouldn't affect them) on the assumption that if a resource is exported with noop = true, it will end up (correctly) being a noop on the collecting node, but I haven't tested this. Yes. I understand that this would be a change to current behavior, and I'd be perfectly happy with making that a configuration option, so those of us who want the behavior to change have to explicitly specify it, so long as it's mentioned clearly in the Exported Resouces docs (one of my big gripes with this ticket is that as far as I know, there's nothing clear in the docs to explain that --noop runs still export resources). Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this
Jira (PUP-1079) Exported resources is exporting to the database with --noop flag
Title: Message Title Rob Nelson commented on PUP-1079 Re: Exported resources is exporting to the database with --noop flag Deepak Giridharagopal For me, I'd say that noop, by definition, should not be expected to effect actual changes, so both facts and resources should not be exported. Since the master or agent in a masterless setup are what send the data to puppetdb, I feel any change in behavior should be made there, including config options. Otherwise, data could be sent over the wire that shouldn't be, even if puppetdb discards it. Even with encryption that's still putting some data at risk and increasing the network load. As mentioned, the docs don't explain this behavior and I would be surprised if new users expected this behavior, so it may be beneficial to set any new option to default to off in the next major release. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-170) exported resources with single element arrays aren't arrays on the collected side
Title: Message Title Francois Lafont commented on PDB-170 Re: exported resources with single element arrays aren't arrays on the collected side Hi, I have exactly the same problem with this environment: OS = Debian Wheezy Puppet = 3.7.3 Ruby = 1.9.3p194 Regards. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
