Jira (PUP-10964) unable to use package task to install gems with puppet_gem provider on Windows
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-10964 unable to use package task to install gems with puppet_gem provider on Windows Change By: Gheorghe Popescu Release Notes Summary: When puppet is used as a library, `environment.bat` is not sourced and this leads to `PUPPET_DIR` to not be set. Because `puppet_gem` is relying on that to build the `gem.bat` path, it will end-up using a non-existing path, making this provider not suitable. Updated the puppet_gem provider to use `Gem.default_bindir` to determine the location of the executables. To avoid accidental usage of `puppet_gem` provider with system ruby, a confine to the existence of `aio_agent_version` fact has been added. 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.390822.1615550747000.2928.1617774120056%40Atlassian.JIRA.
Jira (PUP-10964) unable to use package task to install gems with puppet_gem provider on Windows
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-10964 unable to use package task to install gems with puppet_gem provider on Windows Change By: Gheorghe Popescu Release Notes: Bug Fix 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.390822.1615550747000.2929.1617774120118%40Atlassian.JIRA.
Jira (PUP-11022) Running `bundle exec rake/rspec spec` has failures on main branch
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-11022 Running `bundle exec rake/rspec spec` has failures on main branch Change By: Mihai Buzgau Labels: tech-debt 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.394276.1617737537000.2927.1617773760026%40Atlassian.JIRA.
Jira (PUP-11015) The "posix" provider of the "exec" resource does not fullfil the documentation
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-11015 The "posix" provider of the "exec" resource does not fullfil the documentation Change By: Mihai Buzgau Labels: community 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.394250.1617733822000.2926.1617773700041%40Atlassian.JIRA.
Jira (PUP-10959) Lock loaders using a single central lock
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10959 Lock loaders using a single central lock Change By: Josh Cooper Fix Version/s: PUP 7.6.0 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.390496.1615338623000.2925.1617771060046%40Atlassian.JIRA.
Jira (PDB-5096) Add some initial command processing tests
Title: Message Title Rob Browning created an issue PuppetDB / PDB-5096 Add some initial command processing tests Issue Type: Improvement Assignee: Unassigned Components: PuppetDB Created: 2021/04/06 5:41 PM Priority: Normal Reporter: Rob Browning Add an initial tool (say ext/bin/check-command-perf ... stockpile-queue.tgz or something) to run some command processing tests against puppetdb, likely via ./pdb, when given a stockpile queue archive. It's fine for it to be a requirement that lein uberjar has already been run. For now, this is just testing command processing, i.e. what's described intentionally side-steps the command ingestion (via http) costs. For the initial version, let's just assume we're using pdbbox, and PDBBOX is set in the environment, and assume pdb is stopped. Then, we'll require that the $PDBBOX/var/stockpile/cmd/q dir be empty, untar the archive into the $PDBBOX/stockpile/cmd/q dir, start ./pdb services -c "$PDBBOX/pdb.ini", and time how long it takes for the queue to become empty. Let's also check relevant metrics at the end to make sure nothing unexpected has happened (i.e. too many commands deferred or sent to the DLO, etc.). Given the metrics checks, we might want to consider writing this in something like clojure (perhaps as a lein alias), python, or ruby, though it might also be feasible in bash with help from jq. At the moment, one way to create a suitable stockpile queue from an existing timeshifted database, for the purposes of working on this ticket, would be to export the database via the archive endpoint, create a new pdbbox, make sure postgresql is stopped, import the export, and then cd "$PDBBOX/var/stockpile/q" && tar czpSf ../stockpile.tgz .. In the longer run, we may want to augment the command described in PDB-5095 to support an output option for writing directly to a stockpile queue instead of a wireformat archive, which should be reasonably easy, and much more efficient than having to round-trip through an export. Perhaps
Jira (PDB-5095) Add a tool to timeshift archive exports
Title: Message Title
Rob Browning created an issue
PuppetDB / PDB-5095
Add a tool to timeshift archive exports
Issue Type:
Improvement
Assignee:
Unassigned
Components:
PuppetDB
Created:
2021/04/06 5:29 PM
Priority:
Normal
Reporter:
Rob Browning
Add a (for now) dev-only lein alias to timeshift wire format exports (produced by the pdb archive endpoint). Perhaps something like this:
lein timeshift-export --timeshift-to now -o timeshifted.tgz original.tgz
See the :install-gems alias in project.clj for an example:
:install-gems {:source-paths ^:replace ["src-gems"]
:target-path "target-gems"
:dependencies
Jira (PDB-5094) Add some initial command processing tests
Title: Message Title Rob Browning created an issue PuppetDB / PDB-5094 Add some initial command processing tests Issue Type: Improvement Assignee: Unassigned Components: PuppetDB Created: 2021/04/06 5:21 PM Priority: Normal Reporter: Rob Browning Add an initial tool (say ext/bin/check-query-perf or something) to run a query performance test (for now just capturing query execution times) against puppetdb, likely via ./pdb, when given a set of queries and the pdb address (or could just default to localhost:8080 for now). It's fine for it to be a requirement that lein uberjar has already been run. One place we might consider storing the queries, if they're not sensitive, is somewhere in dev-resources/. It's completely fine for the first implementation to be as simple as (effectively) running time curl ... -d@query-file > /dev/null once for each query and saving the times somewhere for later processing. We'll probably also eventually want some way, perhaps via gnuplot, or matplotlib to quickly compare results, but that can be addressed separately. Capturing the execution times, can support that work, and future possible automated regression testing. While we don't need (and might not want for now) the full automatic PDBBOX creation whenever one isn't already indicated in the environment that ext/bin/render-pdb-schema does, we might want to follow some of the existing argument conventions/behaviors there and in our other tools. For example, if we want to allow specification of the pdb to query, we could use --pgport PGPORT, etc.
Jira (PDB-5094) Add some initial query tests
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5094 Add some initial query tests Change By: Rob Browning Summary: Add some initial command processing query tests 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.394361.1617754897000.2898.1617754920118%40Atlassian.JIRA.
Jira (PDB-2898) Disallow paging query params for PQL queries
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-2898 Disallow paging query params for PQL queries Change By: Zachary Kent Story Points: 2 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.142673.1469120256000.2838.1617751140285%40Atlassian.JIRA.
Jira (PDB-2898) Disallow paging query params for PQL queries
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-2898 Disallow paging query params for PQL queries Change By: Zachary Kent Team: Ghost 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.142673.1469120256000.2840.1617751140373%40Atlassian.JIRA.
Jira (PDB-4766) Allow querying for all reports with type = any
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-4766 Allow querying for all reports with type = any Change By: Zachary Kent Team: Ghost 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.361242.159120288.2837.1617751140239%40Atlassian.JIRA.
Jira (PDB-2898) Disallow paging query params for PQL queries
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-2898 Disallow paging query params for PQL queries Change By: Zachary Kent Labels: query-engine-improvements tsr-pdb-backlog 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.142673.1469120256000.2839.1617751140329%40Atlassian.JIRA.
Jira (PDB-4766) Allow querying for all reports with type = any
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-4766 Allow querying for all reports with type = any Change By: Zachary Kent Labels: query-engine-improvements tsr-pdb-backlog 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.361242.159120288.2836.1617751140189%40Atlassian.JIRA.
Jira (PUP-11002) Expose v4 catalog endpoint for {{Puppet::HTTP::Service::Compiler}}
Title: Message Title
Molly Waggett updated an issue
Puppet / PUP-11002
Expose v4 catalog endpoint for {{Puppet::HTTP::Service::Compiler}}
Change By:
Molly Waggett
Story Points:
3
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.393513.161723397.2581.1617745380140%40Atlassian.JIRA.
Jira (PUP-11002) Expose v4 catalog endpoint for {{Puppet::HTTP::Service::Compiler}}
Title: Message Title
Molly Waggett updated an issue
Puppet / PUP-11002
Expose v4 catalog endpoint for {{Puppet::HTTP::Service::Compiler}}
Change By:
Molly Waggett
The ace-server is currently using a deprecated REST patterns in an indirector implementation to request catalogs from the v4 catalog endpoint. Expose a method for making post requests to the v4 catalog endpoint in {{Puppet::HTTP::Service::Compiler}} . This should have (more-or-less) the same considerations (e.g. logging, testing, etc.) as the corresponding v3 method. I have spiked this out in https://github.com/puppetlabs/puppet/pull/8556
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
Jira (PUP-11002) Expose v4 catalog endpoint for {{Puppet::HTTP::Service::Compiler}}
Title: Message Title
Molly Waggett updated an issue
Puppet / PUP-11002
Expose v4 catalog endpoint for {{Puppet::HTTP::Service::Compiler}}
Change By:
Molly Waggett
Fix Version/s:
PUP 7.y
Fix Version/s:
PUP 6.y
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.393513.161723397.2573.1617745200030%40Atlassian.JIRA.
Jira (PUP-11002) Expose v4 catalog endpoint for {{Puppet::HTTP::Service::Compiler}}
Title: Message Title
Molly Waggett updated an issue
Puppet / PUP-11002
Expose v4 catalog endpoint for {{Puppet::HTTP::Service::Compiler}}
Change By:
Molly Waggett
Sprint:
Skeletor Ready to groom
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.393513.161723397.2569.1617745080096%40Atlassian.JIRA.
Jira (PUP-11022) Running `bundle exec rake/rspec spec` has failures on main branch
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-11022 Running `bundle exec rake/rspec spec` has failures on main branch Change By: Maggie Dreyer Summary: Running `bundle exe exec rake/rspec spec` has failures on main branch 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.394276.1617737537000.2472.1617737640091%40Atlassian.JIRA.
Jira (PUP-11022) Running `bundle exe rake/rspec spec` has failures on main branch
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-11022 Running `bundle exe rake/rspec spec` has failures on main branch Change By: Maggie Dreyer Summary: Running ` bundle exe rake/ rspec spec` has failures on main branch 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.394276.1617737537000.2471.1617737640044%40Atlassian.JIRA.
Jira (PUP-11022) Running `rspec spec` has failures on main branch
Title: Message Title Maggie Dreyer created an issue Puppet / PUP-11022 Running `rspec spec` has failures on main branch Issue Type: Bug Assignee: Unassigned Created: 2021/04/06 12:32 PM Priority: Normal Reporter: Maggie Dreyer Running the Puppet specs using bundle exec rspec spec or bundle exec rake spec consistently produces these failures: https://gist.github.com/pcarlisle/42b9792d2f1d997d24c7f6736bfb8473. We can reproduce this in both a mac and a linux environment. When those files are run individually or when using the parallel_spec rake task, nothing fails. So it would appear there's some kind of order dependent issue that's not getting picked up by Travis, which uses parallel_spec. Add Comment
Jira (PUP-11004) Backport logic to detect migrated CA dir location
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-11004 Backport logic to detect migrated CA dir location Change By: Maggie Dreyer Release Notes Summary: Puppet will now report the right value for the `cadir` setting after migrating the CA. 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.394052.1617643715000.2418.1617735120030%40Atlassian.JIRA.
Jira (PUP-11004) Backport logic to detect migrated CA dir location
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-11004 Backport logic to detect migrated CA dir location Change By: Maggie Dreyer Release Notes: Enhancement 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.394052.1617643715000.2417.1617735060035%40Atlassian.JIRA.
Jira (PUP-11015) The "posix" provider of the "exec" resource does not fullfil the documentation
Title: Message Title Felix moved an issue Puppet / PUP-11015 The "posix" provider of the "exec" resource does not fullfil the documentation Change By: Felix Key: CPR PUP - 776 11015 Project: Community Package Repository Puppet 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.394250.1617733822000.2379.1617733920039%40Atlassian.JIRA.
Jira (FACT-2984) Facter 4 outputs mountpoints facts differently on macOS
Title: Message Title Josh Cooper commented on FACT-2984 Re: Facter 4 outputs mountpoints facts differently on macOS Passed CI in puppet-agent#7c742fd310a1e06bc483fa92464e1a3e8ff8884b but we'll need a version of puppet 6 with the facterng bump to confirm it works. 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.391211.1615903504000.2310.1617731880032%40Atlassian.JIRA.
Jira (FACT-3004) Do not auto promote dotted facts to structured
Title: Message Title Josh Cooper updated an issue Facter / FACT-3004 Do not auto promote dotted facts to structured Change By: Josh Cooper Flagged: Impediment 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.393702.1617359453000.2282.1617731340034%40Atlassian.JIRA.
Jira (PUP-10853) When blocking legacy facts in puppet7, puppet agent run fails to fetch 'operatingsystem' fact
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10853 When blocking legacy facts in puppet7, puppet agent run fails to fetch 'operatingsystem' fact Change By: Josh Cooper Flagged: Impediment 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.383136.1610563179000.2278.1617731280118%40Atlassian.JIRA.
Jira (FACT-2958) Fact names with dots shouldn't be converted to structured facts
Title: Message Title Josh Cooper updated an issue Facter / FACT-2958 Fact names with dots shouldn't be converted to structured facts Change By: Josh Cooper Flagged: Impediment 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.390115.1614917343000.2279.1617731280164%40Atlassian.JIRA.
Jira (FACT-3000) Dot notation implemented in Facter 4 is incomplete
Title: Message Title Josh Cooper updated an issue Facter / FACT-3000 Dot notation implemented in Facter 4 is incomplete Change By: Josh Cooper Flagged: Impediment 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.393010.1616788653000.2281.1617731280260%40Atlassian.JIRA.
Jira (FACT-3002) Add feature flag that ignores quotation in Facter 3
Title: Message Title Josh Cooper updated an issue Facter / FACT-3002 Add feature flag that ignores quotation in Facter 3 Change By: Josh Cooper Flagged: Impediment 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.393405.1617177937000.2280.1617731280208%40Atlassian.JIRA.
Jira (FACT-3004) Do not auto promote dotted facts to structured
Title: Message Title Josh Cooper commented on FACT-3004 Re: Do not auto promote dotted facts to structured Holding off on resolving this as there is some discussion around the name of the facter setting 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.393702.1617359453000.2202.1617729600133%40Atlassian.JIRA.
Jira (PUP-10973) `puppet facts diff` output should be pretty
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10973 `puppet facts diff` output should be pretty Change By: Josh Cooper Release Notes: Enhancement Release Notes Summary: The "puppet facts diff" command now pretty prints its JSON output. The older form can be specified using "--render_as json". 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.392811.1616691172000.2179.1617729360193%40Atlassian.JIRA.
Jira (PUP-10973) `puppet facts diff` output should be pretty
Title: Message Title Josh Cooper commented on PUP-10973 Re: `puppet facts diff` output should be pretty Passed CI in puppet#42cb3a33b8 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.392811.1616691172000.2142.1617729180140%40Atlassian.JIRA.
Jira (PUP-10964) unable to use package task to install gems with puppet_gem provider on Windows
Title: Message Title Josh Cooper commented on PUP-10964 Re: unable to use package task to install gems with puppet_gem provider on Windows Passed CI in puppet#b53337cedb 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.390822.1615550747000.1965.1617725520237%40Atlassian.JIRA.
Jira (FACT-2996) Performance regression gathering networking facts in facter 4.x
Title: Message Title
Ciprian Badescu commented on FACT-2996
Re: Performance regression gathering networking facts in facter 4.x
André Keller, Could you temporarily do the bellow change and provide us a `got undefined method `each' for nil:NilClass` message containing the full backtrace:
diff --git a/lib/facter/resolvers/base_resolver.rb b/lib/facter/resolvers/base_resolver.rb
index a9d0cfd8c..6841f0ec3 100644
--- a/lib/facter/resolvers/base_resolver.rb
+++ b/lib/facter/resolvers/base_resolver.rb
@@ -28,10 +28,10 @@ module Facter
cache_nil_for_unresolved_facts(fact_name)
end
rescue NoMethodError => e
-log.debug("Could not resolve #{fact_name}, got #{e}")
+log.debug("Could not resolve #{fact_name}, got #{e} at #{e.backtrace}")
@fact_list[fact_name] = nil
rescue LoadError, NameError => e
Jira (FACT-3004) Do not auto promote dotted facts to structured
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-3004 Do not auto promote dotted facts to structured Change By: Gheorghe Popescu Release Notes Summary: Changes the way Facter 4 treats dots in fact names, reverting to the same behaviour as Facter 3. This means that by default, any dot in custom or external fact names will be considered as part of the fact name and not a delimiter for structured facts.This also adds a global setting `autopromote-dotted-facts` which can be set to enable the conversion of dotted facts to structured. 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.393702.1617359453000.1725.1617710280042%40Atlassian.JIRA.
Jira (FACT-3004) Do not auto promote dotted facts to structured
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-3004 Do not auto promote dotted facts to structured Change By: Gheorghe Popescu Release Notes: Bug Fix 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.393702.1617359453000.1726.1617710280101%40Atlassian.JIRA.
Jira (FACT-3004) Do not auto promote dotted facts to structured
Title: Message Title
Gheorghe Popescu updated an issue
Facter / FACT-3004
Do not auto promote dotted facts to structured
Change By:
Gheorghe Popescu
Dotted Facter 4 (up to 4.0.52) provides a way to create structured facts from multiple fact definitions. However, the feature is not compatible with other parts of the Puppet ecosystem and can cause facts to be named differently in Facter 4 than in Facter 2/3.In order to avoid changing Puppet manifests, hiera lookups, PE classification rules, dotted facts should not be automatically promoted to structured facts. This functionality can Treating those facts as structured will still be enabled trough possible by usging a global facter setting which by default is set to false.Eg:default behavior{code:ruby}# custom factFacter.add('a.b.c') do setcode { "d" }end# external facta.b.c=dis represented as { "a.b.c": "d" }{code}setting true{code:ruby}# custom factFacter.add('a.b.c') do setcode { "d" }end# external facta.b.c=dis represented as { "a": {"b": { "c": "d"} }{code}
Add Comment
This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Jira (FACT-3004) Do not auto promote dotted facts to structured
Title: Message Title
Gheorghe Popescu updated an issue
Facter / FACT-3004
Do not auto promote dotted facts to structured
Change By:
Gheorghe Popescu
Facter 4 (up to 4.0.52) provides a way to create structured facts from multiple fact definitions. However, the feature is not compatible with other parts of the Puppet ecosystem and can cause facts to be named differently in Facter 4 than in Facter 2/3.In order to avoid changing Puppet manifests, hiera lookups, PE classification rules, dotted custom and external facts should not be automatically promoted to structured facts.Treating those facts as structured will still be possible by usging a global facter setting which by default is set to false.Eg:default behavior{code:ruby}# custom factFacter.add('a.b.c') do setcode { "d" }end# external facta.b.c=dis represented as { "a.b.c": "d" }{code}setting true{code:ruby}# custom factFacter.add('a.b.c') do setcode { "d" }end# external facta.b.c=dis represented as { "a": {"b": { "c": "d"} }{code}
Add Comment
This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
