Jira (PUP-11717) Can't "dig" into facts when legacy facts are excluded
Title: Message Title Ben Ford commented on PUP-11717 Re: Can't "dig" into facts when legacy facts are excluded The PR looks like it also protects fact() from breaking, but maybe worth a quick check. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.479164.1673933795000.2430.1674088980029%40Atlassian.JIRA.
Jira (PUP-11689) Enable strict mode by default
Title: Message Title Ben Ford commented on PUP-11689 Re: Enable strict mode by default I could be mistaken, but I think this means that spec-puppet has had strict_variables on for at least seven years. https://github.com/rodjek/rspec-puppet/blame/master/lib/rspec-puppet/adapters.rb#L153 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.476842.1670862344000.66274.1670965980031%40Atlassian.JIRA.
Jira (PUP-11663) max/min core functions are incorrect for Semver types
Title: Message Title Ben Ford commented on PUP-11663 Re: max/min core functions are incorrect for Semver types Sean Millichamp this doesn't fix the issue, but I've got a simple module that makes versioncmp() easier to use. A PR to add Semver support would be rad. https://github.com/binford2k/binford2k-version Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.473277.1666723189000.52300.1666731780037%40Atlassian.JIRA.
Jira (PUP-11621) Drop Hiera 3 Requirement
Title: Message Title Ben Ford commented on PUP-11621 Re: Drop Hiera 3 Requirement There are only 13 modules on the Forge that implement Hiera 3 backends. Because of how Hiera 5 backends are implemented, I don't know how to programmatically identify them. If you know a way to do that, I can re-run the analysis and omit those that have a 5 backend too. https://docs.google.com/spreadsheets/d/1HmKxSkqk0bxbNNCmuoFLm2MslCbJhu8NtYgOLLN4rTU/edit#gid=278845657 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.465779.1661814931000.25311.1661897580037%40Atlassian.JIRA.
Jira (PUP-11520) Support for SMB authentication on the File resource
Title: Message Title Ben Ford commented on PUP-11520 Re: Support for SMB authentication on the File resource Based on this MS docs page, you'd think that it would be in the dsc/psdscresources module, but I don't see it listed there or in the upstream powershell gallery module. Perhaps ethan might know where the dsc_file resource is. Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.444747.1650906574000.24979.1651786080120%40Atlassian.JIRA.
Jira (PUP-11451) Make collecting exported resources optional
Title: Message Title Ben Ford commented on PUP-11451 Re: Make collecting exported resources optional Likewise, I'm curious to hear about the use case. My concern with this would be the situation where someone enabled this setting maybe not knowing what it did, or forgetting about it later, or maybe not communicating that setting to others on the team, etc. And then later on, a user of that same infrastructure installed a module that used exported resources, say puppetlabs-haproxy or the like, and everything appeared to work fine but it just didn't do anything. That could be immensely frustrating and confusing, and difficult to debug since querying for the exported resources would show them in the database as expected. Asking for community help probably wouldn't even be terribly productive since this setting would be such a change. Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.434328.1643983687000.26892.1646180760029%40Atlassian.JIRA.
Jira (PUP-11368) Can't install the dsc/* modules without explicitly specifying version
Title: Message Title Ben Ford commented on PUP-11368 Re: Can't install the dsc/* modules without explicitly specifying version michael.lombardi should probably be in this conversation too Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.424358.1637328257000.3378.1642615200272%40Atlassian.JIRA.
Jira (PUP-11368) Can't install the dsc/* modules without explicitly specifying version
Title: Message Title Ben Ford commented on PUP-11368 Re: Can't install the dsc/* modules without explicitly specifying version https://jubianchi.github.io/semver-check/#/%3E%3D%200.0.0/2.12.0-0-4 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.424358.1637328257000.799.1638915600034%40Atlassian.JIRA.
Jira (PUP-11368) Can't install the dsc/* modules without explicitly specifying version
Title: Message Title
Ben Ford commented on PUP-11368
Re: Can't install the dsc/* modules without explicitly specifying version
The reason for this problem is complex. The simple version is that we don't just import the DSC resource directly from the PowerShell Gallery, we run it through a build process that repackages and vendors it into a Puppet module along with helper functions. Sometimes we have to make updates to the tool that does that build process, and when we do that, we need to rebuild a new version of the module. We can't just republish the same version number of the module, because there be dragons, so we have to distinguish between and rank builds. We chose to do that via pre-release numbering (version-prerelease (see below), so the referenced dsc-psdscresources-2.0.0-0-3 module is the third build of the psdscresources v2.0.0 DSC module. So why did we use prerelease instead of the build identifier (version+build)? Because semver explicitly discards the build identifier when comparing versions, so dsc-psdscresources-2.0.0+0-1 = dsc-psdscresources-2.0.0+0-2 = dsc-psdscresources-2.0.0+0-3. So this still doesn't let us have a "latest" version. Correcting this means fixing semantic-puppet such that it compares pre-release versions properly. The problem is in the assumption made with the first bullet point of https://github.com/puppetlabs/semantic_puppet/pull/23. If you specify the range as described, it does work according to that design requirement. I believe that is incorrect.
> SemanticPuppet::VersionRange.parse(">= 2.12.0-0") === SemanticPuppet::Version.parse("2.12.0-0-4")
=> true
Related: we also need to iterate on the release numbering anyways, since this scheme will break as soon as we get to double digits. dsc-psdscresources-2.0.0+0-2 will sort lexicographically as greater than dsc-psdscresources-2.0.0+0-12. Tangent: During development, we also specifically chose to require version pinning, since the ecosystem was more volatile than usual. That's no longer the case though.
Add Comment
Jira (FACT-3065) submit facts for new facter releases to facterdb
Title: Message Title Ben Ford commented on FACT-3065 Re: submit facts for new facter releases to facterdb Basically, what we'd probably want to do is hook into the build/packaging CI pipeline. We would need automation to run puppet facts on each supported operating system and save the output to a file, like $ puppet facts > facts/4.2/centos-7-x86_64.facts then create a PR with all the files. Here's an example PR where a community member submitted facts. https://github.com/voxpupuli/facterdb/pull/181 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.412672.1629371747000.129609.1631633280269%40Atlassian.JIRA.
Jira (PUP-11189) Add functions to iterate over files/templates in the current module
Title: Message Title Ben Ford commented on PUP-11189 Re: Add functions to iterate over files/templates in the current module Dirk Heinrichs you might consider building and maintaining this yourself as a module on the Forge. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.408658.1627373801000.119974.1630362840201%40Atlassian.JIRA.
Jira (PUP-10924) `module install` can't unpack modules with long paths because of minitar bug
Title: Message Title Ben Ford commented on PUP-10924 Re: `module install` can't unpack modules with long paths because of minitar bug I cannot reproduce the test failure indicated by https://travis-ci.com/github/puppetlabs/puppet-modulebuilder/jobs/484161960#L423-L430 on a Xenial machine. I removed the validate_ustar_path check from the PDK, then used the code from the unit test to make the deeply nested empty file in a module. I used my modified PDK to build the module package and then puppet module install to install it. Everything worked as expected. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.387906.1613638812000.82939.1626387540109%40Atlassian.JIRA.
Jira (PUP-10924) `module install` can't unpack modules with long paths because of minitar bug
Title: Message Title Ben Ford commented on PUP-10924 Re: `module install` can't unpack modules with long paths because of minitar bug fwiw, I'm unable to replicate this locally (macOS). I removed the path length checks from the PDK and used it to build modules which I then installed with puppet module install. Both the build and the install succeeded until I exceeded the OS/filesystem maximum length, at which point I received an Errno::ENAMETOOLONG as I'd expect. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.387906.1613638812000.80224.1626200040027%40Atlassian.JIRA.
Jira (PUP-11078) puppet generate types should return non-zero when types cannot be generated
Title: Message Title Ben Ford created an issue Puppet / PUP-11078 puppet generate types should return non-zero when types cannot be generated Issue Type: Bug Assignee: Unassigned Created: 2021/06/02 4:44 PM Priority: Normal Reporter: Ben Ford When puppet generate types cannot generate types, it will error, but it explicitly just logs it and keeps going. https://github.com/puppetlabs/puppet/blob/1a13e0cf96c70b303492e684f9ccf4c38207b3dd/lib/puppet/generate/type.rb#L204-L211 [~/.puppetlabs/etc/code/environments/production]$ puppet generate types Notice: Generating Puppet resource types. Error: /Users/ben/.puppetlabs/etc/code/environments/production/modules/drupal/lib/puppet/type/drupal_module.rb: title patterns that use procs are not supported. Error: /Users/ben/.puppetlabs/etc/code/environments/production/modules/drupal/lib/puppet/type/drupal_theme.rb: title patterns that use procs are not supported. Error:
Jira (PDOC-304) Puppet Strings Undocumented Param Detection
Title: Message Title Ben Ford moved an issue Puppet Strings / PDOC-304 Puppet Strings Undocumented Param Detection Change By: Ben Ford Key: PDK PDOC - 1718 304 Project: Puppet Development Kit Strings Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.401062.1622143127000.46874.1622674980130%40Atlassian.JIRA.
Jira (PUP-10641) Puppet Module Tool gives unhelpful error message for bad module name
Title: Message Title Ben Ford assigned an issue to Jesse Scott Puppet / PUP-10641 Puppet Module Tool gives unhelpful error message for bad module name Change By: Ben Ford Assignee: Jesse Scott Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.59877.1417031796000.105048.1608590580116%40Atlassian.JIRA.
Jira (PUP-10641) Puppet Module Tool gives unhelpful error message for bad module name
Title: Message Title Ben Ford commented on PUP-10641 Re: Puppet Module Tool gives unhelpful error message for bad module name Jesse Scott What do you think about these HTTP response? [~]$ curl -i https://forgeapi.puppet.com/v3/modules/ntp [ruby-2.6.5@forge_ruby] HTTP/1.1 400 Bad Request server: nginx date: Mon, 21 Dec 2020 22:39:04 GMT content-type: application/json content-length: 60 cache-control: public, must-revalidate etag: "aebd38f7ea0331d668e149b2a9f58e28" vary: Origin,Accept-Encoding x-content-type-options: nosniff x-app-server: forgeapi/forgeapi-forgenext-app-prod-1.ops.puppetlabs.net x-lb-server: forgenext-lb-prod-1
Jira (PUP-10843) Module tool should check for Forge modules compatibility with running versions of Puppet and Facter
Title: Message Title Ben Ford moved an issue Puppet / PUP-10843 Module tool should check for Forge modules compatibility with running versions of Puppet and Facter Change By: Ben Ford Key: FORGE PUP - 55 10843 Issue Type: New Feature Improvement Project: Puppet Forge Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.21269.1387189431000.105037.1608589980066%40Atlassian.JIRA.
Jira (PUP-10843) Module tool should check for Forge modules compatibility with running versions of Puppet and Facter
Title: Message Title Ben Ford updated an issue Puppet / PUP-10843 Module tool should check for Forge modules compatibility with running versions of Puppet and Facter Change By: Ben Ford Component/s: PMT Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.21269.1387189431000.105038.1608589980111%40Atlassian.JIRA.
Jira (PUP-10824) puppet strings generate: Syntax error at 'apply'
Title: Message Title Ben Ford commented on PUP-10824 Re: puppet strings generate: Syntax error at 'apply' This is being corrected in https://github.com/puppetlabs/puppet-strings/pull/266 Josh Cooper interestingly, tests reveal that the apply behaves differently from other keywords in Puppet itself. My assumption was that with tasks=true that the parser was failing because a keyword was being used as a parameter name. That implies that any keyword should fail similarly, but I tested with if, class, function, case and others. None of them caused a syntax error. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.381096.1608124312000.103779.1608228720236%40Atlassian.JIRA.
Jira (PUP-10823) Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25
Title: Message Title Ben Ford moved an issue Puppet / PUP-10823 Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25 Change By: Ben Ford Key: IAC PUP - 1324 10823 Method Found: Needs Assessment Sub-team: Performance Issue Type: Improvement Bug Project: Infrastructure Automation Content Puppet Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message
Jira (PUP-8971) Agent Functions - Add encrypt/decrypt functions
Title: Message Title Ben Ford updated an issue Puppet / PUP-8971 Agent Functions - Add encrypt/decrypt functions Change By: Ben Ford Zendesk Ticket Count: 1 Zendesk Ticket IDs: 41568 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.263096.1530205428000.59023.1603212180316%40Atlassian.JIRA.
Jira (PUP-7582) Make attempt to export or virtualize a class an error
Title: Message Title Ben Ford commented on PUP-7582 Re: Make attempt to export or virtualize a class an error I said this in slack some time ago, but I should record it on the ticket. Kill it dead. The more hidden "actually, it's not doing what you think you're doing" gotchas we can eliminate, the better. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.19.1495458026000.42092.1600964520086%40Atlassian.JIRA.
Jira (PUP-10641) Puppet Module Tool gives unhelpful error message for bad module name
Title: Message Title Ben Ford commented on PUP-10641 Re: Puppet Module Tool gives unhelpful error message for bad module name Should the PMT validate the name prior to making the request in the first place and just error out? We could also provide a forge search api that returns an array of all module slugs that match the name exactly. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.59877.1417031796000.24990.1598484420134%40Atlassian.JIRA.
Jira (PUP-10641) Puppet Module Tool gives unhelpful error message for bad module name
Title: Message Title Ben Ford assigned an issue to Unassigned Puppet / PUP-10641 Puppet Module Tool gives unhelpful error message for bad module name Change By: Ben Ford Key: FORGE PUP - 228 10641 Assignee: Ryan Coleman Project: Puppet Forge Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.59877.1417031796000.22885.1598318160039%40Atlassian.JIRA.
Jira (FACT-2588) ipa_facts : does not extract info from sssd.conf
Title: Message Title Ben Ford commented on FACT-2588 Re: ipa_facts : does not extract info from sssd.conf This appears to be a part of the joshuabaird/ipaclient module. Filing or contributing a pull request there will probably be your best bet at getting this fixed. Good luck! Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.357061.1588103651000.49288.1588104660026%40Atlassian.JIRA.
Jira (FACT-2582) external data yaml facts don't load Time values
Title: Message Title Ben Ford created an issue Facter / FACT-2582 external data yaml facts don't load Time values Issue Type: Task Assignee: Unassigned Created: 2020/04/27 10:08 PM Priority: Normal Reporter: Ben Ford Facter 4 doesn't load yaml facts the same way that Facter 3 does. (at least on Windows.) Given a yaml file in /facts.d/facts.yaml like so, --- somefact: time: 2020-04-28 01:44:08.148119000 +00:00 Facter 3 will report that value. PS C:\Users\Administrator> facter somefact.time 2020-04-28 01:44:08.148119000 +00:00
Jira (PDOC-297) Add tag for marking class parameters as "advanced"
Title: Message Title Ben Ford commented on PDOC-297 Re: Add tag for marking class parameters as "advanced" Ping Ewoud Kohl van Wijngaarden Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.344978.1580827545000.12804.1580827680039%40Atlassian.JIRA.
Jira (PDOC-297) Add tag for marking class parameters as "advanced"
Title: Message Title Ben Ford created an issue Puppet Strings / PDOC-297 Add tag for marking class parameters as "advanced" Issue Type: Bug Assignee: Unassigned Created: 2020/02/04 6:45 AM Priority: Normal Reporter: Ben Ford It would be nice to be able to differentiate the parameters that are recommended to use and those that are advanced and should rarely be used. Or arbitrary named groups in the docs. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-7541) Explore removing export / collect / virtual / realize syntax
Title: Message Title Ben Ford commented on PUP-7541 Re: Explore removing export / collect / virtual / realize syntax John Bollinger, no. Sorry I wasn't more clear. What I want is for collectors to not implicitly realize, just the same as you do. More specifically, I want collectors to do exactly one thing – just collect resources into a thing that you can do something with. If you want to add relationships, then yes, you can add relationships to a collection. If you want to realize, then yes, you can realize a collection. But simply invoking the collector shouldn't do anything other than collect. That would be a bigger breaking change, since so much current code relies on the side effect, but that's what I'd like long term. I'd also like a better query language, since there's currently not a way to collect "all packages except for those tagged as puppet_enterprise". The manifold type is simply a bandaid to separate the relationship case from the realize case without drastic language changes today. It can also be used on older Puppet versions. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.191187.1494891335000.3615.1580247661655%40Atlassian.JIRA.
Jira (PUP-7541) Explore removing export / collect / virtual / realize syntax
Title: Message Title
Ben Ford commented on PUP-7541
Re: Explore removing export / collect / virtual / realize syntax
I'd like to re-open this conversation. I had another conversation with a community member today who used the same old Yumrepo<| |>->Package<| title != 'yum' |> pattern to lay down internal repositories before any packages were installed. No surprise, he knocked over his whole infrastructure when all Puppet Enterprise packages were installed on all nodes. I do currently have a better solution for that use case in the manifold module. It's an anchor-like resource type that allows you to make meta relationships on real resources only. Aka, it won't realize anything like a collector will. I'd far prefer for this to be baked into the language the way that contain() effectively replaced anchors, but this is far better than collectors can be. A relationship like that would look something like
manifold { 'packages':
type => 'package', # make relationships on packages
match=> 'title', # match their title parameter
pattern => 'yum', # match on title=yum
invert => true,# but invert so title != yum
relationship => before, # and this resource should come before them
}
yumrepo { 'internal':
ensure => 'present',
Jira (PUP-10250) is it time to remove deprecated hiera_* functions?
Title: Message Title
Ben Ford updated an issue
Puppet / PUP-10250
is it time to remove deprecated hiera_* functions?
Change By:
Ben Ford
Functions like {{hiera_hash()}} have been [deprecated for three years|https://github.com/puppetlabs/puppet/blame/master/lib/puppet/functions/hiera_hash.rb#L5] now. Is Puppet 7 the right time to remove them? There are still 146 modules that use this function, but we could create a puppet-lint plugin to help update these.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.343329.1579817502000.35669.157981874%40Atlassian.JIRA.
Jira (PUP-10250) is it time to remove deprecated hiera_* functions?
Title: Message Title Ben Ford created an issue Puppet / PUP-10250 is it time to remove deprecated hiera_* functions? Issue Type: Improvement Assignee: Unassigned Created: 2020/01/23 2:11 PM Priority: Normal Reporter: Ben Ford Functions like hiera_hash() have been deprecated for three years now. Is Puppet 7 the right time to remove them? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-10178) split function shouldn't coerce strings to regex
Title: Message Title
Ben Ford created an issue
Puppet / PUP-10178
split function shouldn't coerce strings to regex
Issue Type:
Bug
Assignee:
Unassigned
Created:
2019/12/17 11:17 AM
Priority:
Normal
Reporter:
Ben Ford
The split() function turns strings into regexes internally, which is not intuitive and leads to surprising results.
$ puppet apply -e 'notice("2.6.3".split("."))'
Notice: Scope(Class[main]): []
Notice: Compiled catalog for nyx.local in environment production in 0.03 seconds
Notice: Applied catalog in 0.02 seconds
Of note, this is not what Ruby does:
$ ruby -e "puts '2.6.3'.split('.').inspect"
Jira (PUP-10139) Deferring template rendering is awkward
Title: Message Title
Ben Ford updated an issue
Puppet / PUP-10139
Deferring template rendering is awkward
Change By:
Ben Ford
Currently users have to jump through awkward hoops to render secrets agent side:{code}$variables = { 'password' => Deferred('vault_lookup::lookup', ["secret/test", 'https://vault.docker:8200']),}# compile the template source into the catalogfile { '/etc/secrets.conf': ensure => file, content => Deferred('inline_epp', [file('mymodule/secrets.conf.epp'), $variables]),}{code}The problem with the solution is that the *template* file has to be stored in the *files* directory and that's super unintuitive.After some conversation in Slack, I'm proposing a {{find_template()}} function that would make this make a lot more sense in that the template source is still stored in the traditional {{templates}} directory .{code}$variables = { 'password' => Deferred('vault_lookup::lookup', ["secret/test", 'https://vault.docker:8200']),}# compile the template source into the catalogfile { '/etc/secrets.conf': ensure => file, content => Deferred('inline_epp', [find_template('mymodule/secrets.conf.epp').file, $variables]),}{code}
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-10139) Deferring template rendering is awkward
Title: Message Title
Ben Ford commented on PUP-10139
Re: Deferring template rendering is awkward
Josh Cooper currently yes, the template file needs to be in the files directory. This PR adds the ability to get the source of a file in the templates directory by using find_template('name.epp").file)
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.335042.1573673832000.32790.1573752000251%40Atlassian.JIRA.
Jira (PUP-10139) Deferring template rendering is awkward
Title: Message Title Ben Ford commented on PUP-10139 Re: Deferring template rendering is awkward https://github.com/puppetlabs/puppet/pull/7840 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.335042.1573673832000.30816.1573674061310%40Atlassian.JIRA.
Jira (PUP-10139) Deferring template rendering is awkward
Title: Message Title
Ben Ford created an issue
Puppet / PUP-10139
Deferring template rendering is awkward
Issue Type:
Bug
Assignee:
Unassigned
Created:
2019/11/13 11:37 AM
Priority:
Normal
Reporter:
Ben Ford
Currently users have to jump through awkward hoops to render secrets agent side:
$variables = {
'password' => Deferred('vault_lookup::lookup',
["secret/test", 'https://vault.docker:8200']),
}
# compile the template source into the catalog
file { '/etc/secrets.conf':
Jira (PUP-9186) Deferred doesn't work in 'notify' resource
Title: Message Title Ben Ford commented on PUP-9186 Re: Deferred doesn't work in 'notify' resource Henrik Lindberg before I re-open or open a new ticket, is there work towards making client side templates easier to do? It's a very similar problem, and I solved it the same way you did above, but Eric Sorenson thought that it was a dirty approach. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.278010.1538087632000.29593.1573606500449%40Atlassian.JIRA.
Jira (PDOC-292) Pull defaults from data directory
Title: Message Title Ben Ford commented on PDOC-292 Re: Pull defaults from data directory This would be incredibly useful. I can see the output getting VERY long though, especially if we iterate supported platforms. I wonder if this is worth another PARAMETER_DEFAULTS.md doc? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.327485.1569942028000.123261.1569951720100%40Atlassian.JIRA.
Jira (BOLT-1456) bolt debug output shows task input as a ruby hash, not json
Title: Message Title
Ben Ford created an issue
Puppet Task Runner / BOLT-1456
bolt debug output shows task input as a ruby hash, not json
Issue Type:
Bug
Assignee:
Unassigned
Created:
2019/07/03 4:58 PM
Priority:
Normal
Reporter:
Ben Ford
For example,
Running '/var/folders/km/cz24f0_j1bs4sh93q82sftp0gq/T/d20190703-40142-1rj497t/swagger_gen_post_usersuser_idplaylistsplaylist_idtracks.rb' with {"endpoint_api"=>"https://api.spotify.com/v1", "token"=>"BQAkqyzq6RUTfZ4-epCjQbXS4zVS57YRCYGd6S2MDIzR7D4hjSfXN2PNgUWR4m7Guei4jIWfRqJQxklo88NyjPTGodWmVpcC8Yf2JeIREPkMFE8TzHcpbPpts9PYYUvN4XFzzN8BSWRe2JxrNs9AdoikJ0eqXj7CM2biNJhDMecOHpWWkQEiFPYk0zbtEybOvEPbBL_R07cIJDd3g3KmgQ1LUu4RUDU", "playlist_id"=>"spotify:playlist:4zHrEyszkWe0Owxw44YjEL", "uris"=>"spotify:track:5osIjZhkEUjH4d2qtGd367", "_task"=>"gen::swagger_gen_post_usersuser_idplaylistsplaylist_idtracks"}
if that output were a JSON hash, then I could easily cut it to the command line to debug my task.
Jira (PDOC-265) @example doesn't work with 4.x functions
Title: Message Title Ben Ford commented on PDOC-265 Re: @example doesn't work with 4.x functions Yes, the regsubst docs on the docs site are in pretty poor state. What do we need to do to prioritize fixing this? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9561) puppet language functions are 11,350x slower than ruby functions
Title: Message Title
Ben Ford commented on PUP-9561
Re: puppet language functions are 11,350x slower than ruby functions
After Puppet 6.3, this could be rewritten as something like (eyeball compiled only)
$system_info.group_by |$rec| { $rec['system_id'] }
.filter |$k, $v| { $v.size > 1}
.keys
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
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
Jira (PUP-9561) puppet language functions are 11,350x slower than ruby functions
Title: Message Title Ben Ford commented on PUP-9561 Re: puppet language functions are 11,350x slower than ruby functions I've had similar conversations with two other people in recent weeks. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9561) puppet language functions are 11,350x slower than ruby functions
Title: Message Title
Ben Ford created an issue
Puppet / PUP-9561
puppet language functions are 11,350x slower than ruby functions
Issue Type:
Task
Assignee:
Unassigned
Components:
Language
Created:
2019/03/14 11:16 AM
Priority:
Normal
Reporter:
Ben Ford
From Slack: https://puppetcommunity.slack.com/archives/CFD8Z9A4T/p1552586549522900 I wrote a Puppet language function to, given an array of hashes, return a hash that counted duplicate instances of one of the keys in the original hash and then returned all of the values where the count was > 1. this was the code:
# Find count of records with duplicates:
$id_count = $system_info.reduce({}) |$results, $rec| {
$id = $rec['system_id']
$current = $results[$id].lest || { 0 }
$results + {$id => $current + 1}
Jira (PUP-9561) puppet language functions are 11,350x slower than ruby functions
Title: Message Title Ben Ford updated an issue Puppet / PUP-9561 puppet language functions are 11,350x slower than ruby functions Change By: Ben Ford Reporter: Ben Ford Sean Millichamp Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-523) Make it possible to declare classes, defines and functions (and more) as private to a module
Title: Message Title Ben Ford commented on PUP-523 Re: Make it possible to declare classes, defines and functions (and more) as private to a module What about adding a list of private class names to metadata.json instead? That wouldn't require any keyword changes or extra functions and it would be forwards/backwards compatible. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1126) Make hands on lab more windows friendly
Title: Message Title Ben Ford created an issue Puppet Task Runner / BOLT-1126 Make hands on lab more windows friendly Issue Type: Bug Assignee: Unassigned Created: 2019/02/12 1:42 PM Priority: Normal Reporter: Ben Ford The hands on lab is great, but it doesn't talk about windows very much (ps1 scripts / winrm mentions). It almost feels hostile to windows users. It would be great if some scripts were written in powershell and if there were some labs on interfacing with Windows specific features, like the registry or such. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1126) Make hands on lab more windows friendly
Title: Message Title Ben Ford commented on BOLT-1126 Re: Make hands on lab more windows friendly ping Derek Robinson Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-495) Incorrect known_hosts checking
Title: Message Title Ben Ford commented on BOLT-495 Re: Incorrect known_hosts checking This PR might resolve it: https://github.com/net-ssh/net-ssh/pull/656 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8971) Agent Functions - Add encrypt/decrypt functions
Title: Message Title
Ben Ford commented on PUP-8971
Re: Agent Functions - Add encrypt/decrypt functions
Also, by wrapping the functions into a third function, you can make the use even simpler.
some_class(Sensitive $password) {
some_resource { 'example':
password => $password.secret
}
}
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8971) Agent Functions - Add encrypt/decrypt functions
Title: Message Title Ben Ford commented on PUP-8971 Re: Agent Functions - Add encrypt/decrypt functions When this is released, I'd like to know so that I can deprecate node_encrypt in favor of core functionality. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9424) Certification login
Title: Message Title Ben Ford commented on PUP-9424 Re: Certification login We've found an account with the email address doubled up as you described and corrected it. Please try password recovery and see if you can access your account now. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9424) Certification login
Title: Message Title Ben Ford commented on PUP-9424 Re: Certification login I've requested his username and email address in a reddit DM and will share out-of-bounds when I've got it. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9424) Certification login
Title: Message Title Ben Ford assigned an issue to Christopher Harry Puppet / PUP-9424 Certification login Change By: Ben Ford Assignee: Christopher Harry Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9424) Certification login
Title: Message Title Ben Ford commented on PUP-9424 Re: Certification login I've been working with him on https://www.reddit.com/r/Puppet/comments/aecr0x/support_contact_info_for_nonenterprise_users/ I think that Christopher Harry can help here. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9325) incorrect compiler error while
Title: Message Title
Ben Ford updated an issue
Puppet / PUP-9325
incorrect compiler error while
Change By:
Ben Ford
[This manifest|https://github.com/nrvale0/puppet-site/blob/master/manifests/init.pp] should not compile due to the {{site}} keyword, but instead it warns about {{class}}. This is super confusing to the end user. {code} ✔ ~ (2.5.1@puppet)12:39 $ cat init.ppclass site inherits ::site::params {}✔ ~ (2.5.1@puppet)12:37 $ puppet parser validate init.ppError: Could not parse for environment production: 'class' keyword not allowed at this location (file: /Users/ben/ tmp/ init.pp, line: 1, column: 1){code}
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
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
Jira (PUP-9325) incorrect compiler error while
Title: Message Title
Ben Ford created an issue
Puppet / PUP-9325
incorrect compiler error while
Issue Type:
Bug
Assignee:
Unassigned
Components:
Compiler
Created:
2018/11/20 12:43 PM
Priority:
Normal
Reporter:
Ben Ford
This manifest should not compile due to the site keyword, but instead it warns about class. This is super confusing to the end user.
✔ ~ (2.5.1@puppet)
12:39 $ cat init.pp
class site inherits ::site::params {
}
✔ ~ (2.5.1@puppet)
12:37 $ puppet parser validate init.pp
Jira (PUP-9271) 5.5.7 introduced backwards incompatibility with legacy functions that referenced ruby functions defined in the file
Title: Message Title Ben Ford commented on PUP-9271 Re: 5.5.7 introduced backwards incompatibility with legacy functions that referenced ruby functions defined in the file The issue is masked by PUP-9270, because raising the exception fails due to an uninitialized object. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9270) puppet 5.5.7 causes a stacktrace with puppetlabs-mysql 5.x series
Title: Message Title Ben Ford commented on PUP-9270 Re: puppet 5.5.7 causes a stacktrace with puppetlabs-mysql 5.x series The exception raised on line #L36 references an object not created until line #L44 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9270) puppet 5.5.7 causes a stacktrace with puppetlabs-mysql 5.x series
Title: Message Title
Ben Ford updated an issue
Puppet / PUP-9270
puppet 5.5.7 causes a stacktrace with puppetlabs-mysql 5.x series
Change By:
Ben Ford
*Puppet Version: 5.5.7* *Puppet Server Version:* *OS Name/Version: CentOS 7*The puppet-nova unit tests that consume puppetlabs-mysql 5.2.1 are failing with: {code} Evaluation Error: Error while evaluating a Function Call, undefined local variable or method `created' for Puppet::Pops::Loader::RubyLegacyFunctionInstantiator:Class (file: /home/zuul/workspace/spec/fixtures/modules/mysql/manifests/server.pp, line: 52, column: 14) on node centos-7-rax-ord-030381 {code} *Desired Behavior:*No failure from puppet. *Actual Behavior:* Running the unit tests testing with puppetlabs-mysql 5.2.1 causes the following stack trace: {code} http://logs.openstack.org/46/613446/1/check/puppet-openstack-unit-5.5-centos-7/40e8913/job-output.txt.gz#_2018-10-26_03_45_55_0039752018-10-26 03:45:55.002558 | centos-7 | 1) nova::db::mysql_api on debian-8-x86_64 configures nova::db::mysql_api with only required params should contain Openstacklib::Db::Mysql[nova_api] with user => "nova_api", password_hash => "*AA1420F182E88B9E5F874F6FBE7459291E8F4601", charset => "utf8" and collate => "utf8_general_ci"2018-10-26 03:45:55.002632 | centos-7 | Failure/Error:2018-10-26 03:45:55.002790 | centos-7 | it { is_expected.to contain_openstacklib__db__mysql('nova_api').with(2018-10-26 03:45:55.002886 | centos-7 | :user => 'nova_api',2018-10-26 03:45:55.003035 | centos-7 | :password_hash => '*AA1420F182E88B9E5F874F6FBE7459291E8F4601',2018-10-26 03:45:55.003125 | centos-7 | :charset => 'utf8',2018-10-26 03:45:55.003246 | centos-7 | :collate => 'utf8_general_ci',2018-10-26 03:45:55.003316 | centos-7 | )}2018-10-26 03:45:55.003357 | centos-7 |2018-10-26 03:45:55.003442 | centos-7 | Puppet::PreformattedError:2018-10-26 03:45:55.003975 | centos-7 | Evaluation Error: Error while evaluating a Function Call, undefined local variable or method `created' for Puppet::Pops::Loader::RubyLegacyFunctionInstantiator:Class (file: /home/zuul/workspace/spec/fixtures/modules/mysql/manifests/server.pp, line: 52, column: 14) on node centos-7-rax-ord-0303812018-10-26 03:45:55.004198 | centos-7 | Shared Example Group: "nova::db::mysql_api" called from ./spec/classes/nova_db_mysql_api_spec.rb:812018-10-26 03:45:55.004425 | centos-7 | # ./.bundled_gems/gems/puppet-5.5.7/lib/puppet/pops/loader/ruby_legacy_function_instantiator.rb:36:in `create'2018-10-26 03:45:55.004629 | centos-7 | # ./.bundled_gems/gems/puppet-5.5.7/lib/puppet/pops/loader/module_loaders.rb:263:in `instantiate'2018-10-26 03:45:55.004818 | centos-7 | # ./.bundled_gems/gems/puppet-5.5.7/lib/puppet/pops/loader/module_loaders.rb:237:in `find'2018-10-26 03:45:55.005017 | centos-7 | # ./.bundled_gems/gems/puppet-5.5.7/lib/puppet/pops/loader/base_loader.rb:161:in `internal_load'2018-10-26 03:45:55.005220 | centos-7 | # ./.bundled_gems/gems/puppet-5.5.7/lib/puppet/pops/loader/base_loader.rb:42:in `load_typed'2018-10-26 03:45:55.005423 | centos-7
Jira (PDOC-268) Colliding internal anchors on autogenerated pages
Title: Message Title Ben Ford created an issue Puppet Strings / PDOC-268 Colliding internal anchors on autogenerated pages Issue Type: Bug Assignee: Unassigned Created: 2018/10/17 3:07 AM Priority: Normal Reporter: Ben Ford When different elements have parameters with the same name, the internal anchors can collide. This means, for example, that the documentation on the Forge provides links that go to the wrong place. Example: Load the puppetlabs/mysql reference page. Scroll down to see the sql task entry in the table of contents and click it. Observe that you're now looking at the sql parameter of the mysql::db defined type. Add Comment This message was sent by Atlassian JIRA
Jira (PUP-9242) Vox Pupuli needs guidance for supporting Puppet 6
Title: Message Title Ben Ford created an issue Puppet / PUP-9242 Vox Pupuli needs guidance for supporting Puppet 6 Issue Type: Task Assignee: Eric Sorenson Components: Community Created: 2018/10/16 9:39 AM Priority: Normal Reporter: Ben Ford Vox Pupuli has put together a document of what they think needs to be done for Puppet 6 support. But they would like it to be reviewed and improved. Could someone provide them with feedback? https://github.com/voxpupuli/plumbing/issues/172 Add Comment This
Jira (PUP-9190) Puppet should ignore empty init.pp
Title: Message Title
Ben Ford updated an issue
Puppet / PUP-9190
Puppet should ignore empty init.pp
Change By:
Ben Ford
Puppet6 will error if a module contains an empty init.pp. The [module documentation|https://puppet.com/docs/puppet/5.3/modules_fundamentals.html ] says, "init.pp: Contains a class definition. The init.pp class, if used, is the main class of the module. This class's name must match the module's name."So the init.pp file is optional, but we don't specify whether the file can exist, but be empty or if it only contains a defined type.We discovered in Modules MODULES -7854 that some people may have empty {{init.pp}} and puppet should be more lenient. For now, we removed the empty init.pp from the rspec-puppet's module fixtures./cc [~henrik.lindberg], [~kris.bosland], [~ben.ford], [~chuck], [~eric.sorenson]
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe
Jira (PUP-9190) Puppet should ignore empty init.pp
Title: Message Title Ben Ford updated an issue Puppet / PUP-9190 Puppet should ignore empty init.pp Change By: Ben Ford Attachment: empty_init-pp.csv Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8701) Update to Puppet help in Pup-8646 as removed 'help easter egg' please put it back!
Title: Message Title
Ben Ford updated an issue
Puppet / PUP-8701
Update to Puppet help in Pup-8646 as removed 'help easter egg' please put it back!
Change By:
Ben Ford
*Puppet Version: 5.5* *Puppet Server Version:2018.1* *OS Name/Version: all*Describe your issue in as much detail as possible…`puppet help help help help help` is an ages old 'feature' of puppet help, it's an awesome ice breaker and demo tool for tasks etc. In seriousness the fix is incorrect it allows you to run:puppet helppuppet help helppuppet help help helppuppet help help help help with no error and just the help page being served it only serves the error at the 5th help?*Desired Behavior:*Put it back, `puppet help help help help help` should render asci image {code}$ puppet help help help help help -( _%_/ \ ' /_ - (_) - _%%%/ \% / , \ %\\ \_ %% \ \\ )/\_/ /(___. \ '' (/ )---/(_ __ _ ___ ___ __ _ _ _ _ _ ___ / )---...___ =-= = -_= -=_= _-=_-_ -=- =-_,' ( ```--.._= -_= -_= _-=- -_= _=- ,-') ``--._=-_ =-=_-= _-= _ '-._'-..___( ``-._=_-=_- =_-= ``---__) `-._-=_-_=- )|)| `-._=-_gnv '-'-.\_ `-.RELAX, TODAY IS THE FIRST DAY OF THE REST OF YOUR LIFE.Error: Puppet help only takes two (optional) arguments: a subcommand and an actionError: Try 'puppet help help help' for usage{code}puppet help help should render with colorization or with error to direct people to use the command on another subcommand. puppet help help help help help help ... should render warning*Actual Behavior:*nice error message appears {code:java}root@master:~ # puppet help help help help helpError: The 'puppet help' command takes two (optional) arguments: a subcommand and an actionError: Try 'puppet help help help' for usage {code}
Add Comment
Jira (PDB-3922) Build from source instructions don't work outside our network
Title: Message Title Ben Ford created an issue PuppetDB / PDB-3922 Build from source instructions don't work outside our network Issue Type: Task Assignee: Unassigned Components: DOCS Created: 2018/05/07 11:47 AM Priority: Normal Reporter: Ben Ford The instructions at https://puppet.com/docs/puppetdb/latest/install_from_source.html#step-2-option-a-install-from-source apparently don't work outside of our internal network because during the ezbake step, it makes a network request to artifactory.delivery.puppetlabs.net and then fails because that name doesn't resolve outside our network. Add Comment
Jira (FACT-1845) Facter does not scan default global external fact directories when running as an unprivileged user
Title: Message Title Ben Ford commented on FACT-1845 Re: Facter does not scan default global external fact directories when running as an unprivileged user Fwiw, it's designed that way. https://puppet.com/docs/facter/latest/custom_facts.html#fact-locations I don't know why though. If a non-root user can read the contents of a fact file, then they can read it with or without facter's help, so it doesn't seem to be much use as access control. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8631) --tags should override individual --skip_tags
Title: Message Title Ben Ford commented on PUP-8631 Re: --tags should override individual --skip_tags I think the generalizable solution here is that there should be a way of indicating that --tags and --skip_tags are inverses of each other (or something like inverse) and have the one specified at the more specific scope take precedence. In other words, whichever was specified at the command line would override the other. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8002) "Attempt to redefine entity" caused by using a resource collector
Title: Message Title Ben Ford commented on PUP-8002 Re: "Attempt to redefine entity" caused by using a resource collector I have a customer hitting this error regularly now. Thomas Hallgren is this fixed? Did it get released? Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7822) Make the fact() function from stdlib part of core puppet so that the dot syntax is available in the DSL by default
Title: Message Title Ben Ford commented on PUP-7822 Re: Make the fact() function from stdlib part of core puppet so that the dot syntax is available in the DSL by default I very much like the function solution. I think the most user friendly solution is just making facts dot-accessible without extra language decoration, so that the fact looks exactly the same whether on the CLI (facter networking.interfaces.en0.ip) and in the language ($networking.interfaces.en0.ip), but I can see that being rather difficult to implement. The function is a close second. However, I dislike the .get() name. I very much prefer the .value() name that I proposed earlier. The reason for that is that .get() implies an imperative action, and .value() feels more declarative. We all know that the language itself is not declarative, that it instead builds a declarative catalog, but I think it's prudent to take the opportunity to encourage people to think about what things are rather than instructions to do things. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8101) Optional[] data type doesn't allow a parameter to be disabled
Title: Message Title Ben Ford commented on PUP-8101 Re: Optional[] data type doesn't allow a parameter to be disabled What is specified is: Giving an attribute value of undef to a resource means that the default value for that attribute should be used. That's fine, but I'd also like to be able so pass false to say "don't do this". I'm not trying to overload what undef is. I want some way to say (for example) that the parameter is [some,array,of,things] + false and it does not seem straightforward to do that at all. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8101) Optional[] data type doesn't allow a parameter to be disabled
Title: Message Title Ben Ford commented on PUP-8101 Re: Optional[] data type doesn't allow a parameter to be disabled I guess that I don't really see what the point of Optional is if it's so difficult to make an optional parameter. I don't think that a user should have to jump through hoops to do what seems like a straightforward task. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8101) Optional[] data type doesn't allow a parameter to be disabled
Title: Message Title
Ben Ford created an issue
Puppet / PUP-8101
Optional[] data type doesn't allow a parameter to be disabled
Issue Type:
Bug
Assignee:
Henrik Lindberg
Components:
Language, Language Specification, Type System
Created:
2017/10/27 10:39 AM
Priority:
Normal
Reporter:
Ben Ford
This is easiest to describe with a simple code example
class example (
Optional[String] $param = 'some non undef default value',
) {
# $param
Jira (PUP-8101) Optional[] data type doesn't allow a parameter to be disabled
Title: Message Title
Ben Ford updated an issue
Puppet / PUP-8101
Optional[] data type doesn't allow a parameter to be disabled
Change By:
Ben Ford
This is easiest to describe with a simple code example{code}class example (Optional[String] $param = 'some non undef default value',) {# $param is always set to the default string can never be undef , no matter what you pass in# if you pass in undef, then the default is used# it's effectively impossible to "disable", even though it's Optional}{code}Proposal:I would like the {{Optional}} type to be an enum of the passed in data type, {{Undef}}, and {{false}}. If that were the case, I could pass {{false}} to the class above and achieve the desired results. This could *almost* be done today with {{Variant\[String, Boolean]}}, but then the user could pass in {{true}}, which isn't a member of the desired set of input values.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
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 https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8002) "Attempt to redefine entity" caused by using a resource collector
Title: Message Title Ben Ford created an issue Puppet / PUP-8002 "Attempt to redefine entity" caused by using a resource collector Issue Type: Bug Affects Versions: PUP 4.10.4 Assignee: Unassigned Created: 2017/09/28 9:59 AM Priority: Major Reporter: Ben Ford See PUP-7650 for the root cause of the issue. This behaviour is also sometimes (indeterminately) cause by using a resource collector, and that does not seem to be corrected by the patch linked in PUP-7650 . The error thrown is: Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Virtual Query, Could not autoload puppet/type/pe_ini_setting: Attempt to redefine entity 'http://puppet.com/2016.1/runtime/type/pe_ini_setting'. Set at unknown location at /etc/puppetlabs/code/modules/classroom/manifests/master/student_environment.pp:51:3 on node superdog.puppetlabs.vm
Jira (PUP-8001) "Attempt to redefine entity" caused by using a resource collector
Title: Message Title Ben Ford updated an issue Puppet / PUP-8001 "Attempt to redefine entity" caused by using a resource collector Change By: Ben Ford Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8001) "Attempt to redefine entity" caused by using a resource collector
Title: Message Title Thomas Hallgren created an issue Puppet / PUP-8001 "Attempt to redefine entity" caused by using a resource collector Issue Type: Bug Affects Versions: PUP 4.10.1 Assignee: Unassigned Created: 2017/09/28 9:54 AM Fix Versions: PUP 4.10.3, PUP 5.0.0 Priority: Critical Reporter: Thomas Hallgren A load of a resource type will sometimes create a Puppet::Pops::Loader::TypedName that starts with an uppercase letter. When this name is used in order to find a type generated with puppet generate types, it isn't found. Since it's not found, a load of the Ruby type is performed instead, which results in an "Attempt to redefine entity" error when that a successful load of the generated type has been performed earlier (with a TypedName that didn't start with an uppercase letter).
Jira (PUP-7798) trouble upgrading java-1.8.0-openjdk rpm
Title: Message Title
Ben Ford updated an issue
Puppet / PUP-7798
trouble upgrading java-1.8.0-openjdk rpm
Change By:
Ben Ford
To reproduce, I start out on a CentOS system and run "yum -y update". This installs the following (using bash as a baseline comparison here since it's ubiquitous):{ { code} [root@puppetmaster7 ~]# rpm -qa | egrep '^(bash|java)'bash-4.1.2-48.el6.x86_64java-1.8.0-openjdk-1.8.0.141-2.b16.el6_9.x86_64java-1.8.0-openjdk-headless-1.8.0.141-2.b16.el6_9.x86_64 {code } } Then I downgrade them:{{yum -y downgrade bash java-1.8.0-openjdk java-1.8.0-openjdk-headless}}{ { code} [root@puppetmaster7 ~]# rpm -qa | egrep '^(bash|java)' bash-4.1.2-15.el6_5.2.x86_64java-1.8.0-openjdk-1.8.0.131-0.b11.el6_9.x86_64java-1.8.0-openjdk-headless-1.8.0.131-0.b11.el6_9.x86_64 {code } } Now when I have a bash-updating package resource, I see bash-upgrading lines in the debug output. {{ puppet apply --debug /tmp/b.pp | tee /tmp/bb }} { { code} [root@puppetmaster7 ~]# cat /tmp/b.pp package { 'bash': ensure => latest,}[root@puppetmaster7 ~]# grep bash /tmp/bbDebug: Facter: root:x:0:0:root:/root:/bin/bash "bash;4.1.2;15.el6_5.2",Debug: /Stage[main]/Main/Package[bash]/ensure: bash "4.1.2-15.el6_5.2" is installed, latest is "0:4.1.2-48.el6"Debug: Package[bash](provider=yum): Ensuring => latestDebug: Executing: '/bin/rpm -q bash --nosignature --nodigest --qf '%{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n''Debug: Package[bash](provider=yum): Ensuring latest, so using updateDebug: Executing: '/usr/bin/yum -d 0 -e 0 -y update bash'Debug: /Stage[main]/Main/Package[bash]/ensure: bash "4.1.2-15.el6_5.2" is installed, latest is "0:4.1.2-48.el6"Notice: /Stage[main]/Main/Package[bash]/ensure: ensure changed '4.1.2-15.el6_5.2' to '0:4.1.2-48.el6'Debug: /Stage[main]/Main/Package[bash]: The container Class[Main] will propagate my refresh event {code } } However when I try the same thing with the java rpm, I do not see the same output. {{ puppet apply --debug /tmp/h.pp | tee /tmp/yy }} { { code} [root@puppetmaster7 ~]# cat /tmp/h.pp package { 'java-1.8.0-openjdk': ensure => latest,}[root@puppetmaster7 ~]# grep java /tmp/yyDebug: Loading facts from /etc/puppetlabs/code/environments/common_common/modules/java/lib/facter/java_patch_level.rbDebug: Loading facts from /etc/puppetlabs/code/environments/common_common/modules/java/lib/facter/java_libjvm_path.rbDebug: Loading facts from /etc/puppetlabs/code/environments/common_common/modules/java/lib/facter/java_version.rbDebug: Loading facts from /etc/puppetlabs/code/environments/common_common/modules/java/lib/facter/java_default_home.rbDebug: Loading facts from /etc/puppetlabs/code/environments/common_common/modules/java/lib/facter/java_major_version.rbDebug: Loading facts from /opt/puppetlabs/puppet/cache/lib/facter/java_patch_level.rbDebug: Loading facts from /opt/puppetlabs/puppet/cache/lib/facter/java_libjvm_path.rbDebug: Loading facts from /opt/puppetlabs/puppet/cache/lib/facter/java_version.rbDebug: Loading facts from /opt/puppetlabs/puppet/cache/lib/facter/java_default_home.rbDebug: Loading facts from /opt/puppetlabs/puppet/cache/lib/facter/java_major_version.rbDebug: Facter: searching for operatingsystem.rb in
Jira (PUP-7738) "puppet module install" failes on Puppet 5.0.0
Title: Message Title Ben Ford commented on PUP-7738 Re: "puppet module install" failes on Puppet 5.0.0 Robert Heinzmann Can you check your quoting, escaping, etc? What does your pipeline look like? It appears to work here on CentOS 7, root@master:~ # /usr/local/bin/puppet --version 5.0.0 root@master:~ # /usr/local/bin/puppet module install --version 4.17.1 --target-dir //.tmp/librarian/cache/source/puppet/forge/forgeapi_puppetlabs_com/puppetlabs-stdlib/4.17.1 --module_repository https://forgeapi.puppetlabs.com --modulepath //.tmp/librarian/cache/source/puppet/forge/forgeapi_puppetlabs_com/puppetlabs-stdlib/4.17.1 --module_working_dir //.tmp/librarian/cache/source/puppet/forge/forgeapi_puppetlabs_com/puppetlabs-stdlib/4.17.1 --ignore-dependencies puppetlabs-stdlib Warning: Support for ruby version 2.0.0 is deprecated and will be removed in a future release. See https://docs.puppet.com/puppet/latest/system_requirements.html#ruby for a list of supported ruby versions. (at /usr/local/share/gems/gems/puppet-5.0.0/lib/puppet.rb:181:in `') Notice: Preparing to install into //.tmp/librarian/cache/source/puppet/forge/forgeapi_puppetlabs_com/puppetlabs-stdlib/4.17.1 ... Notice: Downloading from https://forgeapi.puppetlabs.com ... Notice: Installing -- do not interrupt ...
Jira (PUP-7040) Non-existent services throw an error when attempting to disable them
Title: Message Title
Ben Ford commented on PUP-7040
Re: Non-existent services throw an error when attempting to disable them
What if the error was changed to a warning instead? I can see lots of opportunity for mistakes if it just silently ate the error. For example,
service {'cupsd':
enable => false,
}
is a perfectly reasonable bit of code to use accidentally and if Puppet didn't warn you, you might never know.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
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
Jira (PUP-2551) Certname must be lowercase error not helpful
Title: Message Title Ben Ford commented on PUP-2551 Re: Certname must be lowercase error not helpful #puppethack learning opportunity Get started with simple changes to Puppet's configuration settings and defaults. Contribute to Puppet docs. skills Basic ruby Hints: See defaults.rb#L688 Add a warning such as the one suggested above Add the same warning to the docs page. https://github.com/puppetlabs/puppet-docs/blob/master/source/puppet/5.0/configuration.md Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2820) "Array" settings get misleading formatting for default values and error reporting
Title: Message Title
Ben Ford commented on PUP-2820
Re: "Array" settings get misleading formatting for default values and error reporting
#puppethack learning opportunity
Get started with Puppet's configuration settings and defaults. Learn how to validate changes to Puppet core as part of the pull request process.
skills
Ruby, rspec
Hints:
See defaults.rb#L82
The :default value should probably be an empty string. To print an array as a comma separated list, you'd use something like value.join(',')
Grep the codebase for :array to find other occurrences.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
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 https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5196) puppet module tool validates the wrong directory when used w/ --environment
Title: Message Title Ben Ford commented on PUP-5196 Re: puppet module tool validates the wrong directory when used w/ --environment root@master:~ # puppet module install puppetlabs/motd --environment binford2k Notice: Preparing to install into /etc/puppetlabs/code/environments/binford2k/modules ... Notice: Created target directory /etc/puppetlabs/code/environments/binford2k/modules Notice: Downloading from https://forgeapi.puppet.com ... Error: Could not install module 'puppetlabs-motd' (latest) Installation would overwrite /etc/puppetlabs/code/modules/motd Use `puppet module install --force` to install this module anyway Add Comment
Jira (PDOC-164) PDF module documentation
Title: Message Title Ben Ford commented on PDOC-164 Re: PDF module documentation if it's a choice between markdown and PDF, I'd choose markdown every time. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1349) testing custom fact via RUBYLIB causes segfaults
Title: Message Title Ben Ford commented on FACT-1349 Re: testing custom fact via RUBYLIB causes segfaults It doesn't segfault anymore, but it does print an error when the RUBYLIB includes a trailing slash. That error does not show without the slash. root@master:/etc/puppetlabs/code-staging/modules/classroom # RUBYLIB=$(pwd)/lib/ facter hostpubkey /opt/puppetlabs/puppet/lib/libfacter.so: warning: already initialized constant Facter::FACTERVERSION ... Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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
Jira (FACT-1349) testing custom fact via RUBYLIB causes segfaults
Title: Message Title Ben Ford commented on FACT-1349 Re: testing custom fact via RUBYLIB causes segfaults Peter Huene is this still an issue? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7361) Apparently a Puppet Hiera error message points to a 404
Title: Message Title Ben Ford created an issue Puppet / PUP-7361 Apparently a Puppet Hiera error message points to a 404 Issue Type: Bug Assignee: Unassigned Created: 2017/03/15 10:55 PM Priority: Normal Reporter: Ben Ford The new Puppet version is pointing Hiera users to a 404 page. [21:58:28] This is an upgrade of PE 2016.5.1 -> 2017.1 [21:58:31] if it matters [21:58:53] 2017-03-16 04:01:12,660 - [Warning]: /etc/puppetlabs/enterprise/hiera.yaml: Use of 'hiera.yaml' version 3 is deprecated. It should be converted to version 5 [21:58:55] (in /etc/puppetlabs/enterprise/hiera.yaml) [21:58:57] 2017-03-16 04:01:12,833 - [Warning]: The function 'hiera' is deprecated in favor of using 'lookup'. See https://docs.puppet.com/puppet/4.9.4/reference/deprecated_language.html [21:58:59] (file & line not available) [21:59:02] And puppet 4.9.4 Add Comment
Jira (PUP-7360) Apparently a Puppet Hiera error message points to a 404
Title: Message Title Ben Ford created an issue Puppet / PUP-7360 Apparently a Puppet Hiera error message points to a 404 Issue Type: Bug Assignee: Unassigned Created: 2017/03/15 10:01 PM Priority: Normal Reporter: Ben Ford The new Puppet version is pointing Hiera users to a 404 page. [21:58:28] This is an upgrade of PE 2016.5.1 -> 2017.1 [21:58:31] if it matters [21:58:53] 2017-03-16 04:01:12,660 - [Warning]: /etc/puppetlabs/enterprise/hiera.yaml: Use of 'hiera.yaml' version 3 is deprecated. It should be converted to version 5 [21:58:55] (in /etc/puppetlabs/enterprise/hiera.yaml) [21:58:57] 2017-03-16 04:01:12,833 - [Warning]: The function 'hiera' is deprecated in favor of using 'lookup'. See https://docs.puppet.com/puppet/4.9.4/reference/deprecated_language.html [21:58:59] (file & line not available) [21:59:02] And puppet 4.9.4 Add Comment
Jira (PUP-5626) Missing the dependencies key in metadata.json breaks puppet module tool
Title: Message Title
Ben Ford updated an issue
Puppet / PUP-5626
Missing the dependencies key in metadata.json breaks puppet module tool
Change By:
Ben Ford
h1. The Problem If the {{metadata.json}} file is missing a {{dependencies}} key it renders the puppet module tool inoperable. By extension any spec tests that use forge modules also break.{code}root@master:~ # puppet module listError: No dependencies module metadata provided for pe_inifileError: No dependencies module metadata provided for pe_inifileError: Try 'puppet help module list' for usage{code}h1. The workaroundAdding {{"dependencies": []}} to { { metadata.json}} will make it work.h1. The Suggested SolutionPMT should handle the case where the dependencies key is missing better.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
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 https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6240) Deprecate old semantic version implementation
Title: Message Title Ben Ford commented on PUP-6240 Re: Deprecate old semantic version implementation Is this intended to print deprecation warnings during normal operation? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6864) non existing env causes undefined method `environment_data_provider' for nil:NilClass error
Title: Message Title Ben Ford commented on PUP-6864 Re: non existing env causes undefined method `environment_data_provider' for nil:NilClass error Eric Thompson Sure. Delete an existing environment but don't edit classification in the Console. (the console won't allow you to assign to a nonexistent env). Restart the master or clear its cache. Run the agent. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4963) "puppet module build" fails on FIPS-enabled system
Title: Message Title Ben Ford commented on PUP-4963 Re: "puppet module build" fails on FIPS-enabled system puppet module install also fails in Puppet 3.8. Is this ticket still an issue on current Puppet? [root@test-dib centos]# puppet module install --debug --verbose jfryman-selinux Notice: Preparing to install into /etc/puppet/modules ... Notice: Downloading from https://forgeapi.puppetlabs.com ... Info: Resolving dependencies ... Info: Preparing to install ... md5_dgst.c(80): OpenSSL internal error, assertion failed: Digest MD5 forbidden in FIPS mode! Abortado Add Comment
Jira (PUP-6864) non existing env causes undefined method `environment_data_provider' for nil:NilClass error
Title: Message Title Ben Ford commented on PUP-6864 Re: non existing env causes undefined method `environment_data_provider' for nil:NilClass error How would I go about doing that? Is that one of the releases on getpe? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6864) non existing env causes undefined method `environment_data_provider' for nil:NilClass error
Title: Message Title Ben Ford commented on PUP-6864 Re: non existing env causes undefined method `environment_data_provider' for nil:NilClass error 2016-12-14 11:07:52,467 WARN [qtp206485107-403] [p.e.s.f.file-sync-versioned-code-service] Environment 'oink' could not be found, code-id cannot be calculated. 2016-12-14 11:07:52,750 INFO [qtp206485107-403] [puppetserver] Puppet 'replace_facts' command for oink.puppetlabs.vm submitted to PuppetDB with UUID 827cb114-092c-4a2a-a1dd-16398cc2aff2 2016-12-14 11:07:53,083 INFO [qtp206485107-403] [puppetserver] Puppet Caching node for oink.puppetlabs.vm 2016-12-14 11:07:53,116 WARN [qtp206485107-403] [puppetserver] Puppet Class 'settings' is already defined; cannot redefine at : 2016-12-14 11:07:53,159 ERROR [qtp206485107-403] [puppetserver] Puppet Puppet::Parser::Compiler failed with error NoMethodError: undefined method `environment_data_provider' for nil:NilClass on node oink.puppetlabs.vm /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/data_providers/lookup_adapter.rb:232:in `initialize_env_provider' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/data_providers/lookup_adapter.rb:188:in `env_provider' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/data_providers/lookup_adapter.rb:95:in `lookup_in_environment'
Jira (PUP-7000) PMT should remind user to pluginsync
Title: Message Title
Ben Ford updated an issue
Puppet / PUP-7000
PMT should remind user to pluginsync
Change By:
Ben Ford
When the user installs a module with ` {{ puppet module install ` }} and types are installed/updated, it should print a warning out that pluginsync should be run on the master before it can be used.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
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 https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7001) CodeManager should remind user to pluginsync
Title: Message Title Ben Ford created an issue Puppet / PUP-7001 CodeManager should remind user to pluginsync Issue Type: Bug Assignee: Unassigned Created: 2016/12/12 3:13 PM Priority: Normal Reporter: Ben Ford When the user installs a module with `puppet module install` and types are installed/updated, it should print a warning out that pluginsync should be run on the master before it can be used. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7000) PMT should remind user to pluginsync
Title: Message Title Ben Ford created an issue Puppet / PUP-7000 PMT should remind user to pluginsync Issue Type: Bug Assignee: Unassigned Created: 2016/12/12 3:12 PM Priority: Normal Reporter: Ben Ford When the user installs a module with `puppet module install` and types are installed/updated, it should print a warning out that pluginsync should be run on the master before it can be used. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6909) useradd.rb report error
Title: Message Title
Ben Ford commented on PUP-6909
Re: useradd.rb report error
From IRC, the reporter claims that the declaration causing his issue is below. I cannot get any more context from them.
@user::managed{'wwwi':
uid => '30265',
name_comment => 'admins',
tag => [ 'internals', 'admins' ],
}
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6864) undefined method `environment_data_provider' for nil:NilClass
Title: Message Title Ben Ford created an issue Puppet / PUP-6864 undefined method `environment_data_provider' for nil:NilClass Issue Type: Bug Assignee: Unassigned Components: Puppet Server Created: 2016/11/02 10:30 AM Priority: Normal Reporter: Ben Ford In the edge case in which a node group is configured to use an environment which doesn't exist, the compiler sometimes blows up spectacularly with a stack traces and an error message like the following: Puppet::Parser::Compiler failed with error NoMethodError: undefined method `environment_data_provider' for nil:NilClass This can easily occur if the node group is configured to use environments deployed via Code Manager, and then the branch representing the environment is deleted & deployed.
