Jira (PUP-10137) HTTP Retry after 408 request timeout or 504 gateway timeout

2020-04-10 Thread Charlie Sharpsteen (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Charlie Sharpsteen commented on  PUP-10137  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: HTTP Retry after 408 request timeout or 504 gateway timeout   
 

  
 
 
 
 

 
 I can't think of a Puppet API that currently uses the 408 or 504 status codes. So, this would mostly be fore retrying requests to 3rd party APIs. This would be useful, but I haven't heard any requests for it and it could also be implemented in the logic of a custom function or provider that needed it.  
 

  
 
 
 
 

 
 
 

 
 
 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.334641.1573589453000.36194.1586553240040%40Atlassian.JIRA.


Jira (PDB-2398) PuppetDB should enable emergency deletion of historical data

2020-04-10 Thread Austin Blatt (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Austin Blatt assigned an issue to Austin Blatt  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-2398  
 
 
  PuppetDB should enable emergency deletion of historical data   
 

  
 
 
 
 

 
Change By: 
 Austin Blatt  
 
 
Release Notes: 
 New Feature  
 
 
Release Notes Summary: 
 Adds a puppetdb subcommand, `delete-reports`, that will stop PuppetDB and delete all reports and their resource events.   
 
 
Assignee: 
 Austin Blatt  
 
 
Resolution: 
 Fixed  
 
 
Status: 
 Accepted Resolved  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)  
 
 

 
   
 

  
 

   

Jira (PDB-2398) PuppetDB should enable emergency deletion of historical data

2020-04-10 Thread Austin Blatt (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Austin Blatt updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-2398  
 
 
  PuppetDB should enable emergency deletion of historical data   
 

  
 
 
 
 

 
Change By: 
 Austin Blatt  
 
 
Fix Version/s: 
 PDB 5.2.14  
 
 
Fix Version/s: 
 PDB 6.10.0  
 

  
 
 
 
 

 
 
 

 
 
 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.115454.1454725161000.35748.1586535300057%40Atlassian.JIRA.


Jira (FACT-2546) Don't re-load config file when reading block groups

2020-04-10 Thread Bogdan Irimie (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bogdan Irimie created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2546  
 
 
  Don't re-load config file when reading block groups   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2020/04/10 6:09 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Bogdan Irimie  
 

  
 
 
 
 

 
 Fix is implemented in https://github.com/puppetlabs/facter-ng/compare/FACT-2401-extension?expand=1 and should be made after we merge new version of options. (FACT-2401)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)  
 
 

 
  

Jira (FACT-2544) Move cached-custom-facts to a new section in facter.conf

2020-04-10 Thread Mihai Buzgau (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau assigned an issue to Dorin Pleava  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2544  
 
 
  Move cached-custom-facts to a new section in facter.conf   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Assignee: 
 Dorin Pleava  
 

  
 
 
 
 

 
 
 

 
 
 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.355219.1586506973000.35684.1586520960041%40Atlassian.JIRA.


Jira (FACT-2515) Allow facter.conf to define fact groups to be used for blocking or caching

2020-04-10 Thread Florin Dragos (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Florin Dragos assigned an issue to Florin Dragos  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2515  
 
 
  Allow facter.conf to define fact groups to be used for blocking or caching   
 

  
 
 
 
 

 
Change By: 
 Florin Dragos  
 
 
Assignee: 
 Florin Dragos  
 

  
 
 
 
 

 
 
 

 
 
 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.353668.1585746331000.35679.158652067%40Atlassian.JIRA.


Jira (FACT-2527) Fix for tests/ticket_1123_facter_with_invalid_locale.rb

2020-04-10 Thread Oana Tanasoiu (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oana Tanasoiu assigned an issue to Oana Tanasoiu  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2527  
 
 
  Fix for tests/ticket_1123_facter_with_invalid_locale.rb   
 

  
 
 
 
 

 
Change By: 
 Oana Tanasoiu  
 
 
Assignee: 
 Oana Tanasoiu  
 

  
 
 
 
 

 
 
 

 
 
 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.353948.1585825695000.35678.1586519820029%40Atlassian.JIRA.


Jira (PUP-7428) Implement knockout prefix for unique lookups

2020-04-10 Thread Sean Millichamp (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sean Millichamp commented on  PUP-7428  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Implement knockout prefix for unique lookups   
 

  
 
 
 
 

 
 I just encountered the brokenness with knockout_prefix in Hiera's deep merge. I understand that might be a tricky problem to fix, but adding knockout_prefix to Hiera's unique lookup would be relatively easy code. Since Eric Sorenson asked for use-cases above, I was trying to implement a "feature_flag" Hiera setting, implemented as an array of strings. I wanted to be able to list the feature flags but also to negate them as an earlier (more specific) Hiera level, in this case to opt out a small set of customers (who are currently in an extended change freeze) from what would be an otherwise global change on a particular platform type. The deep merge knockout_prefix appeared to work in simple testing, but it is a good thing I did a final full-catalog compile test with octocatalog-diff and caught the problem or I would have ended up violating the customers' change freezes. I ended up whipping up a quick Ruby function applied in the module after Hiera APL that still allowed me to use Hiera's unique merge and get the knockout feature flag behavior for the final set of enabled feature flags, but it would be much cleaner if it were just an option in Hiera's unique merge itself.    
 

  
 
 
 
 

 
 
 

 
 
 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 

Jira (FACT-2545) AIX kernel resovler redirects stderr to stdout, which breaks facts on OS errors

2020-04-10 Thread Ciprian Badescu (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ciprian Badescu updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2545  
 
 
  AIX kernel resovler redirects stderr to stdout, which breaks facts on OS errors   
 

  
 
 
 
 

 
Change By: 
 Ciprian Badescu  
 
 
Sprint: 
 NW - 2020-04-15  
 

  
 
 
 
 

 
 
 

 
 
 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.355220.1586513484000.35659.1586514240032%40Atlassian.JIRA.


Jira (PUP-10414) Windows service calls deprecated `puppet agent --configprint`

2020-04-10 Thread Gheorghe Popescu (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Gheorghe Popescu assigned an issue to Gheorghe Popescu  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10414  
 
 
  Windows service calls deprecated `puppet agent --configprint`   
 

  
 
 
 
 

 
Change By: 
 Gheorghe Popescu  
 
 
Assignee: 
 Gheorghe Popescu  
 

  
 
 
 
 

 
 
 

 
 
 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.354468.1586208728000.35658.1586513640034%40Atlassian.JIRA.


Jira (FACT-2545) AIX kernel resovler redirects stderr to stdout, which breaks facts on OS errors

2020-04-10 Thread Ciprian Badescu (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ciprian Badescu updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2545  
 
 
  AIX kernel resovler redirects stderr to stdout, which breaks facts on OS errors   
 

  
 
 
 
 

 
Change By: 
 Ciprian Badescu  
 
 
Zendesk Ticket Count: 
 1  
 
 
Zendesk Ticket IDs: 
 38720  
 

  
 
 
 
 

 
 
 

 
 
 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.355220.1586513484000.35657.1586513520104%40Atlassian.JIRA.


Jira (FACT-2545) AIX kernel resovler redirects stderr to stdout, which breaks facts on OS errors

2020-04-10 Thread Ciprian Badescu (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ciprian Badescu created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2545  
 
 
  AIX kernel resovler redirects stderr to stdout, which breaks facts on OS errors   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Ciprian Badescu  
 
 
Created: 
 2020/04/10 3:11 AM  
 
 
Labels: 
 jira_escalated  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Ciprian Badescu  
 

  
 
 
 
 

 
 PE version: Reported on 2016.4.10 but present in all versions of PE Facter version: Reported on 3.6.9 but present in all versions of facter The AIX kernel resolver fact runs oslevel -s  and redirects stderr to stdout. If oslevel produces an error, this behavior breaks kernel facts. This in turn breaks kernel fact resolution with no workaround. There's no documented reason why stderr needs to be redirected to stdout here.    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

Jira (PUP-10247) Support ruby 2.7

2020-04-10 Thread Mihai Buzgau (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10247  
 
 
  Support ruby 2.7   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Epic Name: 
 Support ruby 2.7  
 
 
Epic Status: 
 To Do  
 
 
Team: 
 Night's Watch  
 
 
Workflow: 
 Scrum Team Engineering Epic  Workflow  
 
 
Issue Type: 
 Task Epic  
 
 
Status: 
 In Progress Open  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)  
 
 

 
   
 

  

Jira (PUP-10410) package fails on openjdk with non-boolean status string

2020-04-10 Thread Mihai Buzgau (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau commented on  PUP-10410  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: package fails on openjdk with non-boolean status string   
 

  
 
 
 
 

 
 Hi Matt! Puppet supports the following values for ensure property: 
 
present 
absent 
purged 
held 
installed 
latest 
/./ 
 More info here: https://puppet.com/docs/puppet/latest/types/package.html#package-attribute-ensure Can please consider changing your manifest from:  
 
 
 
 
 package { ' java-1.8.0-openjdk-headless':  
 
 
   ensure => true,  
 
 
 }   
 
 
 
  to   
 
 
 
 
 package { ' java-1.8.0-openjdk-headless':  
 
 
   ensure => installed,  
 
 
 }   
 
 
 
  If you want have puppet check if the package is installed and install it if it is not. or  
 
 
 
 
 package { ' java-1.8.0-openjdk-headless':  
 
 

Jira (FACT-2544) Move cached-custom-facts to a new section in facter.conf

2020-04-10 Thread Mihai Buzgau (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2544  
 
 
  Move cached-custom-facts to a new section in facter.conf   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 

  
 
 
 
 

 
 Users should be able to define new fact groups in facter.conf {code}facts : {  blocklist : [ "file system", "EC2", "os.name" ],  ttls : [{ "timezone" : 30 days },  ]}global : {  external-dir : [ "./external_facts"],  custom-dir   : [ "./custom-facts", "./custom-facts2" ],  no-external-facts : false,  no-custom-facts  : false,  no-ruby  : false  show-legacy  : false}cli : {  debug : false,  trace : false,  verbose   : true,}fact-groups: {    my_group: ['value'],   my_group2: ['value2'],    cached-custom-facts: ['',''] }{code}  
 

  
 
 
 
 

 
 
 

 
 
 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 

Jira (FACT-2544) Move cached-custom-facts to a new section in facter.conf

2020-04-10 Thread Bogdan Irimie (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bogdan Irimie updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2544  
 
 
  Move cached-custom-facts to a new section in facter.conf   
 

  
 
 
 
 

 
Change By: 
 Bogdan Irimie  
 

  
 
 
 
 

 
 Users should be able to define new fact groups in facter.conf {code}facts : {  blocklist : [ "file system", "EC2", "os.name" ],  ttls : [{ "timezone" : 30 days },  ]}global : {  external-dir : [ "./external_facts"],  custom-dir   : [ "./custom-facts", "./custom-facts2" ],  no-external-facts : false,  no-custom-facts  : false,  no-ruby  : false  show-legacy  : false}cli : {  debug : false,  trace : false,  verbose   : true,}fact-groups: {    my_group: ['value'],   my_group2: ['value2'],    cached-custom-facts: ['',''] }{code}  
 

  
 
 
 
 

 
 
 

 
 
 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 

Jira (FACT-2544) Move cached-custom-facts to a new section in facter.conf

2020-04-10 Thread Mihai Buzgau (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2544  
 
 
  Move cached-custom-facts to a new section in facter.conf   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 

  
 
 
 
 

 
 Users should be able to define new fact groups in facter.conf {code}facts : {  blocklist : [ "file system", "EC2", "os.name" ],  ttls : [{ "timezone" : 30 days },  ]}global : {  external-dir : [ "./external_facts"],  custom-dir   : [ "./custom-facts", "./custom-facts2" ],  no-external-facts : false,  no-custom-facts  : false,  no-ruby  : false  show-legacy  : false}cli : {  debug : false,  trace : false,  verbose   : true,} facts fact -groups: {    my_group: ['value'],   my_group2: ['value2'],    cached-custom-facts: ['',''] }{code}  
 

  
 
 
 
 

 
 
 

 
 
 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.

Jira (FACT-2544) Move cached-custom-facts to a new section in facter.conf

2020-04-10 Thread Mihai Buzgau (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2544  
 
 
  Move cached-custom-facts to a new section in facter.conf   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Story Points: 
 1  
 

  
 
 
 
 

 
 
 

 
 
 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.355219.1586506973000.35637.1586507220327%40Atlassian.JIRA.


Jira (FACT-2544) Move cached-custom-facts to a new section in facter.conf

2020-04-10 Thread Bogdan Irimie (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bogdan Irimie updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2544  
 
 
  Move cached-custom-facts to a new section in facter.conf   
 

  
 
 
 
 

 
Change By: 
 Bogdan Irimie  
 

  
 
 
 
 

 
 Users should be able to define new fact groups in facter.conf  {code}facts : {  blocklist : [ "file system", "EC2", "os.name" ],  ttls : [{ "timezone" : 30 days },  ]}global : {  external-dir : [ "./external_facts"],  custom-dir   : [ "./custom-facts", "./custom-facts2" ],  no-external-facts : false,  no-custom-facts  : false,  no-ruby  : false  show-legacy  : false}cli : {  debug : false,  trace : false,  verbose   : true,}fact-groups: {   my_group: ['value'],   my_group2: ['value2'],   cached-custom-facts: ['',''] }{code}  
 

  
 
 
 
 

 
 
 

 
 
 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 

Jira (FACT-2544) Move cached-custom-facts to a new section in facter.conf

2020-04-10 Thread Mihai Buzgau (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2544  
 
 
  Move cached-custom-facts to a new section in facter.conf   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sub-team: 
 ghost  
 

  
 
 
 
 

 
 
 

 
 
 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.355219.1586506973000.35634.1586507220236%40Atlassian.JIRA.


Jira (FACT-2544) Move cached-custom-facts to a new section in facter.conf

2020-04-10 Thread Mihai Buzgau (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2544  
 
 
  Move cached-custom-facts to a new section in facter.conf   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Team: 
 Night's Watch  
 

  
 
 
 
 

 
 
 

 
 
 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.355219.1586506973000.35633.1586507220179%40Atlassian.JIRA.


Jira (FACT-2544) Move cached-custom-facts to a new section in facter.conf

2020-04-10 Thread Mihai Buzgau (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2544  
 
 
  Move cached-custom-facts to a new section in facter.conf   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 NW - 2020-04-15  
 

  
 
 
 
 

 
 
 

 
 
 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.355219.1586506973000.35635.1586507220241%40Atlassian.JIRA.


Jira (FACT-2544) Move cached-custom-facts to a new section in facter.conf

2020-04-10 Thread Bogdan Irimie (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bogdan Irimie updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2544  
 
 
  Move cached-custom-facts to a new section in facter.conf   
 

  
 
 
 
 

 
Change By: 
 Bogdan Irimie  
 

  
 
 
 
 

 
 Users should be able to define new fact groups in facter.conf   {code}  facts : {  blocklist : [ "file system", "EC2", "os.name" ],  ttls : [{ "timezone" : 30 days },  ]}global : {  external-dir : [ "./external_facts"],  custom-dir   : [ "./custom-facts", "./custom-facts2" ],  no-external-facts : false,  no-custom-facts  : false,  no-ruby  : false  show-legacy  : false}cli : {  debug : false,  trace : false,  verbose   : true,} fact facts -groups: {   my_group: ['value'],   my_group2: ['value2'],   cached-custom-facts: ['',''] }{code}  
 

  
 
 
 
 

 
 
 

 
 
 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 

Jira (FACT-2544) Move cached-custom-facts to a new section in facter.conf

2020-04-10 Thread Mihai Buzgau (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2544  
 
 
  Move cached-custom-facts to a new section in facter.conf   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Story Points: 
 1 2  
 

  
 
 
 
 

 
 
 

 
 
 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.355219.1586506973000.35638.1586507220371%40Atlassian.JIRA.


Jira (FACT-2544) Move cached-custom-facts to a new section in facter.conf

2020-04-10 Thread Florin Dragos (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Florin Dragos created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2544  
 
 
  Move cached-custom-facts to a new section in facter.conf   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2020/04/10 1:22 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Florin Dragos  
 

  
 
 
 
 

 
 Users should be able to define new fact groups in facter.conf  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)  
 
 

 
   
 
   

Jira (PUP-10375) Latest version ensured for python packages is incorrect

2020-04-10 Thread Luchian Nemes (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Luchian Nemes assigned an issue to Luchian Nemes  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10375  
 
 
  Latest version ensured for python packages is incorrect   
 

  
 
 
 
 

 
Change By: 
 Luchian Nemes  
 
 
Assignee: 
 Luchian Nemes  
 

  
 
 
 
 

 
 
 

 
 
 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.350599.158463166.35616.1586502000189%40Atlassian.JIRA.


Jira (PUP-10417) Custom Ruby functions that define a JSON module can ambiguate its scope and break Puppet

2020-04-10 Thread Henrik Lindberg (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg commented on  PUP-10417  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Custom Ruby functions that define a JSON module can ambiguate its scope and break Puppet   
 

  
 
 
 
 

 
 FWIW, and IIRC - the spec says that it is illegal to define new Ruby constants in a 4.x function. Irrespective of where they end up in the ruby runtime they will cause problems  
 

  
 
 
 
 

 
 
 

 
 
 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.354928.1586391583000.35615.1586501760074%40Atlassian.JIRA.


Jira (FACT-2515) Allow facter.conf to define fact groups to be used for blocking or caching

2020-04-10 Thread Florin Dragos (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Florin Dragos updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2515  
 
 
  Allow facter.conf to define fact groups to be used for blocking or caching   
 

  
 
 
 
 

 
Change By: 
 Florin Dragos  
 
 
Summary: 
 Extract group config file from gem Allow facter.conf to define fact groups to be used for blocking or caching  
 

  
 
 
 
 

 
 
 

 
 
 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.353668.1585746331000.35606.1586500680031%40Atlassian.JIRA.