Jira (PDB-5280) [docs issue] unterminated code block in PuppetDB docs

2022-02-10 Thread Rob Browning (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Browning commented on  PDB-5280  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: [docs issue] unterminated code block in PuppetDB docs   
 

  
 
 
 
 

 
 Looks like the relevant section has moved to migration_coordination.markdown, and I don't see any verbatim issues there now, so think this can be resolved.  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-5280) [docs issue] unterminated code block in PuppetDB docs

2022-02-10 Thread Rob Browning (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Browning assigned an issue to Rob Browning  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-5280  
 
 
  [docs issue] unterminated code block in PuppetDB docs   
 

  
 
 
 
 

 
Change By: 
 Rob Browning  
 
 
Assignee: 
 Rob Browning  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-4316) (docs) Inventory missing from entities page

2022-02-10 Thread Rob Browning (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Browning assigned an issue to Rob Browning  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4316  
 
 
  (docs) Inventory missing from entities page   
 

  
 
 
 
 

 
Change By: 
 Rob Browning  
 
 
Assignee: 
 Rob Browning  
 

  
 
 
 
 

 
 
 

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


Jira (PDOC-305) Puppet docs for the file type are missing available checksum choices

2022-02-10 Thread Heston Hoffman (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Heston Hoffman moved an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Strings /  PDOC-305  
 
 
  Puppet docs for the file type are missing available checksum choices   
 

  
 
 
 
 

 
Change By: 
 Heston Hoffman  
 
 
Key: 
 DOC PDOC - 5153 305  
 
 
Method Found: 
 Needs Assessment  
 
 
Workflow: 
 Documentation Scrum Team  Workflow  
 
 
Project: 
 Documentation [Internal] Puppet Strings  
 

  
 
 
 
 

 
 
 

 
 
 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 

Jira (PUP-11435) Puppet 6.26 and 7.13 may cause specs to fail

2022-02-10 Thread Aria Li (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Aria Li assigned an issue to Aria Li  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-11435  
 
 
  Puppet 6.26 and 7.13 may cause specs to fail   
 

  
 
 
 
 

 
Change By: 
 Aria Li  
 
 
Assignee: 
 Aria Li  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-5451) Slow CTE query after upgrade Postgres to 11 PuppetDB 6.20

2022-02-10 Thread David McTavish (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David McTavish updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-5451  
 
 
  Slow CTE query after upgrade Postgres to 11 PuppetDB 6.20   
 

  
 
 
 
 

 
Change By: 
 David McTavish  
 
 
Epic Link: 
 PE-31891  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-5451) Slow CTE query after upgrade Postgres to 11 PuppetDB 6.20

2022-02-10 Thread Austin Blatt (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Austin Blatt commented on  PDB-5451  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Slow CTE query after upgrade Postgres to 11 PuppetDB 6.20   
 

  
 
 
 
 

 
 Postgres seems to be underestimating the number of rows in your tables. You can find further information here https://www.cybertec-postgresql.com/en/join-strategies-and-performance-in-postgresql/. Under the heading "Impact on query performance" there's an explanation of how this underestimate leads Postgres to pick a plan using a nested loop join that ends up being slower. And following that section, under "How to make PostgreSQL choose the correct join strategy", there are a few additional things you can try. I would try out 

ANALYZE the table, perhaps with increased default_statistics_target
 and  

Configure the parameters that tell PostgreSQL about your hardware and resources: random_page_cost, effective_cache_size and effective_io_concurrency. ...
 The cost estimates of your two queries are very similar 64779.33 vs 65428.57, even though the performance is further apart, so even a small tweak to the hardware cost estimates could lead it to pick the more performant query.  
 

  
 
 
 
 

 
 
 

 
 
 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 

Jira (PUP-11455) Composable termini

2022-02-10 Thread Josh Cooper (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-11455  
 
 
  Composable termini   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2022/02/10 9:56 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Josh Cooper  
 

  
 
 
 
 

 
 Puppet currently only supports a single terminus implementation per model (node, facts, catalog, etc). However, there are times when users want to route to multiple endpoints, such as saving facts to puppetdb and splunk, etc. From glarizza  https://puppetcommunity.slack.com/archives/C0W1X7ZAL/p1629318412042600 From nate.mccurdy https://puppetcommunity.slack.com/archives/C0W1X7ZAL/p1629391266056000 Composable termini thread  https://puppetcommunity.slack.com/archives/C0W1X7ZAL/p1629406416062500 A common workaround for this limitation is to create a new terminus that inherit from another, perform the operation and delegate to the base class. For example, see https://github.com/puppetlabs/puppetlabs-splunk_hec/blob/ebf4f4c206ce29c09e654f4dcfb476e0cc73fd67/lib/puppet/indirector/facts/splunk_hec.rb#L33 https://github.com/puppetlabs/puppetlabs-satellite_pe_tools/blob/73b479b8471d734a414ae87ef8af0738c39b40c3/lib/puppet/indirector/facts/satellite.rb#L26 https://github.com/puppetlabs/puppetlabs-hdp/blob/d78b33e98a40c85d3ef1d96621fbc6c11ab1b096/lib/puppet/indirector/facts/hdp.rb#L36  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

 

Jira (PUP-11440) No option to fail fast when agent-specified environment does not exist

2022-02-10 Thread Nate McCurdy (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nate McCurdy commented on  PUP-11440  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: No option to fail fast when agent-specified environment does not exist   
 

  
 
 
 
 

 
 Having strict mode abort early sounds good to me. But switching to the "production" environment by default in the non-strict mode is still a bit concerning to me. In a setup where there is no server-specified environment, how can we be sure that "production" is the correct one to fall back to? For example, if a chunk of nodes normally run against a canary environment (e.g. -E canary) then want to run against a feature branch but a human typos the name, that node will then revert to production for a run rather than the usual canary environment. We don't currently see this auto-switching behavior in our systems that are running 6.19.1. When did that make it in to Puppet? I see that we should start using strict mode to guard against this problem, but I'm not sure when we need to and when we can. Is that a Puppet 7 only feature?  
 

  
 
 
 
 

 
 
 

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


Jira (PUP-11440) No option to fail fast when agent-specified environment does not exist

2022-02-10 Thread Nate McCurdy (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nate McCurdy updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-11440  
 
 
  No option to fail fast when agent-specified environment does not exist   
 

  
 
 
 
 

 
Change By: 
 Nate McCurdy  
 

  
 
 
 
 

 
 h2. The ProblemWhen using an agent-specified environment workflow and the requested environment does not exist, there is no way to halt the Puppet run early and prevent a catalog compilation.Additionally, the behavior of automatically switching to the "production" environment is unexpected and not desired in an agent-specified environment workflow.This behavior exposes multiple issues... *When not using sctrict_environment_mode:* * The agent gets a 404 from the {{file_metadatas}} endpoint, but it still submits a catalog request: ** {noformat}[root@agent7 ~]# puppet agent -t --environment fake --http_debugInfo: Using environment 'fake'opening connection to server7.vagrant:8140...openedstarting SSL for server7.vagrant:8140...SSL established, protocol: TLSv1.3, cipher: TLS_AES_128_GCM_SHA256<- "GET /puppet/v3/file_metadatas/plugins?recurse=false=manage_type=sha256_per.5-p203 (x86_64-linux)\r\nAccept: application/json, text/pson\r\nAccept-Encoding: gzip;q=1.0,deflate-> "HTTP/1.1 404 Not Found\r\n"-> "Date: Mon, 31 Jan 2022 21:47:28 GMT\r\n"-> "Content-Type: application/json;charset=utf-8\r\n"-> "X-Puppet-Version: 7.14.0\r\n"-> "Content-Length: 87\r\n"-> "\r\n"reading 87 bytes...-> "{\"message\":\"Not Found: Could not find environment 'fake'\",\"issue_kind\":\"RUNTIME_ERROR\"}"read 87 bytesConn keep-aliveNotice: Environment 'fake' not found on server, skipping initial pluginsync.<- "POST /puppet/v3/catalog/agent7.vagrant?environment=fake HTTP/1.1\r\nX-Puppet-Version: 7.14.0\r\n{noformat} *  ** This puts unneeded load on the Puppetserver while it compiles a catalog. * The server responds with a 200, which is odd considering the environment doesn't exist. ** {noformat}-> "HTTP/1.1 200 OK\r\n"-> "Date: Mon, 31 Jan 2022 21:47:28 GMT\r\n"-> "Content-Type: application/vnd.puppet.rich+json; charset=utf-8\r\n"-> "X-Puppet-Version: 7.14.0\r\n" {noformat} * The agent then switches to the "production" environment.  Supposedly  Apparently  because it's server-specified  is "production" . But in my case the external node classifier (ENC) is NOT specifying any environment at all. ** {noformat}Notice: Local environment: 'fake' doesn't match server specified environment 'production', restarting agent run with environment 'production' {noformat} * Here's my ENC script used for testing: ** {code:bash}#!/bin/bashcat <---class: {}parameters: {}EOF {code} * The agent then does pluginsync against the production environment and follows up with another catalog request, this time against production. ** {noformat}<- "POST /puppet/v3/catalog/agent7.vagrant?environment=production HTTP/1.1\r\nX-Puppet-Version: 7.14.0\r\nUser-Agent: Puppet/7.14.0 Ruby/2.7.5-p203 (x86_64-linux)\r\nAccept: application/vnd.puppet.rich+json, application/json, text/pson\r\nContent-Type: application/x-www-form-urlencoded\r\nAccept-Encoding: 

Jira (PUP-11437) puppet lookup fails to interpolate topscope variables when an environment is specified

2022-02-10 Thread Nirupama Mantha (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-11437  
 
 
  puppet lookup fails to interpolate topscope variables when an environment is specified   
 

  
 
 
 
 

 
Change By: 
 Nirupama Mantha  
 
 
Story Points: 
 2  
 

  
 
 
 
 

 
 
 

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


Jira (PUP-11440) No option to fail fast when agent-specified environment does not exist

2022-02-10 Thread Nirupama Mantha (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-11440  
 
 
  No option to fail fast when agent-specified environment does not exist   
 

  
 
 
 
 

 
Change By: 
 Nirupama Mantha  
 
 
Affects Version/s: 
 PUP 6.26.0  
 

  
 
 
 
 

 
 
 

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


Jira (PUP-11440) No option to fail fast when agent-specified environment does not exist

2022-02-10 Thread Nirupama Mantha (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-11440  
 
 
  No option to fail fast when agent-specified environment does not exist   
 

  
 
 
 
 

 
Change By: 
 Nirupama Mantha  
 
 
Story Points: 
 3  
 

  
 
 
 
 

 
 
 

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


Jira (PUP-11453) Remove cron trigger and use snyk org token

2022-02-10 Thread Nirupama Mantha (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-11453  
 
 
  Remove cron trigger and use snyk org token   
 

  
 
 
 
 

 
Change By: 
 Nirupama Mantha  
 
 
Story Points: 
 1  
 

  
 
 
 
 

 
 
 

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


Jira (FACT-3104) Remove cron trigger and use snyk org token

2022-02-10 Thread Nirupama Mantha (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-3104  
 
 
  Remove cron trigger and use snyk org token   
 

  
 
 
 
 

 
Change By: 
 Nirupama Mantha  
 
 
Story Points: 
 1  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-5451) Slow CTE query after upgrade Postgres to 11 PuppetDB 6.20

2022-02-10 Thread David McTavish (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David McTavish updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-5451  
 
 
  Slow CTE query after upgrade Postgres to 11 PuppetDB 6.20   
 

  
 
 
 
 

 
Change By: 
 David McTavish  
 
 
Epic Link: 
 PE-31891  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-5453) PE PDB Extensions status endpoint is broken

2022-02-10 Thread David McTavish (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David McTavish updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-5453  
 
 
  PE PDB Extensions status endpoint is broken   
 

  
 
 
 
 

 
Change By: 
 David McTavish  
 
 
Component/s: 
 PuppetDB  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-5452) Test query performance against JIT enabled Postgres

2022-02-10 Thread David McTavish (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David McTavish updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-5452  
 
 
  Test query performance against JIT enabled Postgres   
 

  
 
 
 
 

 
Change By: 
 David McTavish  
 
 
Component/s: 
 PuppetDB  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-4525) PQL and AST should not return schema errors to user

2022-02-10 Thread David McTavish (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David McTavish updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4525  
 
 
  PQL and AST should not return schema errors to user   
 

  
 
 
 
 

 
Change By: 
 David McTavish  
 
 
Priority: 
 Normal Low  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-4933) query with `in` operator fails

2022-02-10 Thread David McTavish (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David McTavish updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4933  
 
 
  query with `in` operator fails   
 

  
 
 
 
 

 
Change By: 
 David McTavish  
 
 
Priority: 
 Normal Low  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-4875) Add option to log PDBQuery correlation uuids in Postgres

2022-02-10 Thread David McTavish (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David McTavish updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4875  
 
 
  Add option to log PDBQuery correlation uuids in Postgres
 

  
 
 
 
 

 
Change By: 
 David McTavish  
 
 
Priority: 
 Normal Low  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-4688) Remove deprecated config settings in PDB 8.x

2022-02-10 Thread David McTavish (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David McTavish updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4688  
 
 
  Remove deprecated config settings in PDB 8.x   
 

  
 
 
 
 

 
Change By: 
 David McTavish  
 
 
Summary: 
 Remove deprecated config settings  in PDB 8.x  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-4688) Remove deprecated config settings

2022-02-10 Thread David McTavish (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David McTavish updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4688  
 
 
  Remove deprecated config settings   
 

  
 
 
 
 

 
Change By: 
 David McTavish  
 
 
Priority: 
 Normal Low  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-5054) Speed up the currently slow aggregate-event-counts query

2022-02-10 Thread David McTavish (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David McTavish updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-5054  
 
 
  Speed up the currently slow aggregate-event-counts query   
 

  
 
 
 
 

 
Change By: 
 David McTavish  
 
 
Epic Link: 
 PE-31891  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-5334) Improve facts-test/fact-environment-queries performance

2022-02-10 Thread David McTavish (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David McTavish updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-5334  
 
 
  Improve facts-test/fact-environment-queries performance   
 

  
 
 
 
 

 
Change By: 
 David McTavish  
 
 
Summary: 
 Fix Improve  facts-test/fact-environment-queries  performance  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-5054) Speed up the currently slow aggregate-event-counts query

2022-02-10 Thread David McTavish (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David McTavish assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-5054  
 
 
  Speed up the currently slow aggregate-event-counts query   
 

  
 
 
 
 

 
Change By: 
 David McTavish  
 
 
Assignee: 
 Austin Blatt  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-5185) PuppetDB rejects catalogs with tags containing newlines (added automatically by Puppet)

2022-02-10 Thread David McTavish (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David McTavish updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-5185  
 
 
  PuppetDB rejects catalogs with tags containing newlines (added automatically by Puppet)   
 

  
 
 
 
 

 
Change By: 
 David McTavish  
 
 
Priority: 
 Normal Low  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-5277) puppetdb::master::routes decides on facts cache method based on wrong input

2022-02-10 Thread David McTavish (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David McTavish updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-5277  
 
 
  puppetdb::master::routes decides on facts cache method based on wrong input   
 

  
 
 
 
 

 
Change By: 
 David McTavish  
 
 
Labels: 
 low-hanging-fruit  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-4597) Puppetdb module issues notice every run for postgresql-contrib with postgres11 (on Debian Buster)

2022-02-10 Thread David McTavish (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David McTavish updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4597  
 
 
  Puppetdb module issues notice every run for postgresql-contrib with postgres11 (on Debian Buster)   
 

  
 
 
 
 

 
Change By: 
 David McTavish  
 
 
Priority: 
 Normal Low  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-5024) Fix transient error in pe-puppetdb sync test

2022-02-10 Thread David McTavish (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David McTavish updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-5024  
 
 
  Fix transient error in pe-puppetdb sync test   
 

  
 
 
 
 

 
Change By: 
 David McTavish  
 
 
Priority: 
 Normal Low  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-5260) Fix PQL parse performance problems

2022-02-10 Thread David McTavish (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David McTavish updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-5260  
 
 
  Fix PQL parse performance problems   
 

  
 
 
 
 

 
Change By: 
 David McTavish  
 
 
Priority: 
 Normal Low  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-5193) Do first pass jmc profiling of the pdbext endpoints

2022-02-10 Thread David McTavish (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David McTavish updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-5193  
 
 
  Do first pass jmc profiling of the pdbext endpoints   
 

  
 
 
 
 

 
Change By: 
 David McTavish  
 
 
Priority: 
 Normal Low  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-5193) Do first pass jmc profiling of the pdbext endpoints

2022-02-10 Thread David McTavish (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David McTavish updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-5193  
 
 
  Do first pass jmc profiling of the pdbext endpoints   
 

  
 
 
 
 

 
Change By: 
 David McTavish  
 
 
Labels: 
 low-hanging-fruit  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-5195) Analysis of Estate Reporting Queries

2022-02-10 Thread David McTavish (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David McTavish assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-5195  
 
 
  Analysis of Estate Reporting Queries   
 

  
 
 
 
 

 
Change By: 
 David McTavish  
 
 
Assignee: 
 Andrei Filipovici  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-5383) Allow to set maximum-pool-size in docker image

2022-02-10 Thread David McTavish (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David McTavish updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-5383  
 
 
  Allow to set maximum-pool-size in docker image   
 

  
 
 
 
 

 
Change By: 
 David McTavish  
 
 
Labels: 
 low-hanging-fruit  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-4964) Investigate likely effort required to move pdb to its own cluster

2022-02-10 Thread David McTavish (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David McTavish updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4964  
 
 
  Investigate likely effort required to move pdb to its own cluster   
 

  
 
 
 
 

 
Change By: 
 David McTavish  
 
 
Priority: 
 Normal Low  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-4588) After drop-joins percolates a bit, consider enabling it for a few remaining queries

2022-02-10 Thread David McTavish (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David McTavish updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4588  
 
 
  After drop-joins percolates a bit, consider enabling it for a few remaining queries   
 

  
 
 
 
 

 
Change By: 
 David McTavish  
 
 
Priority: 
 Normal Low  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-4462) PuppetDB Log Directory Permissions are Incorrect

2022-02-10 Thread David McTavish (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David McTavish updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4462  
 
 
  PuppetDB Log Directory Permissions are Incorrect   
 

  
 
 
 
 

 
Change By: 
 David McTavish  
 
 
Labels: 
 security  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-5215) Diagnose and fix pdb SIGHUP handling

2022-02-10 Thread David McTavish (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David McTavish updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-5215  
 
 
  Diagnose and fix pdb SIGHUP handling   
 

  
 
 
 
 

 
Change By: 
 David McTavish  
 
 
Priority: 
 Normal Low  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-5229) CentOS 8 package uses legacy path in tmpfiles

2022-02-10 Thread David McTavish (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David McTavish updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-5229  
 
 
  CentOS 8 package uses legacy path in tmpfiles   
 

  
 
 
 
 

 
Change By: 
 David McTavish  
 
 
Labels: 
 low-hanging-fruit  security  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-5192) Start decreasing the (spurious) test logging

2022-02-10 Thread David McTavish (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David McTavish updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-5192  
 
 
  Start decreasing the (spurious) test logging   
 

  
 
 
 
 

 
Change By: 
 David McTavish  
 
 
Priority: 
 Normal Low  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-5192) Start decreasing the (spurious) test logging

2022-02-10 Thread David McTavish (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David McTavish assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-5192  
 
 
  Start decreasing the (spurious) test logging   
 

  
 
 
 
 

 
Change By: 
 David McTavish  
 
 
Assignee: 
 Rob Browning  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-5192) Start decreasing the (spurious) test logging

2022-02-10 Thread David McTavish (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David McTavish updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-5192  
 
 
  Start decreasing the (spurious) test logging   
 

  
 
 
 
 

 
Change By: 
 David McTavish  
 
 
Labels: 
 low-hanging-fruit  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-4805) Don't defer shutdown for cases intended to be immediate

2022-02-10 Thread David McTavish (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David McTavish updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4805  
 
 
  Don't defer shutdown for cases intended to be immediate   
 

  
 
 
 
 

 
Change By: 
 David McTavish  
 
 
Priority: 
 Normal Low  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-4520) Jenkins PR status only reflects ezbake build status

2022-02-10 Thread David McTavish (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David McTavish updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4520  
 
 
  Jenkins PR status only reflects ezbake build status   
 

  
 
 
 
 

 
Change By: 
 David McTavish  
 
 
Priority: 
 Normal Low  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-4586) Always look for include_facts_expiration in the engine

2022-02-10 Thread David McTavish (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David McTavish updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4586  
 
 
  Always look for include_facts_expiration in the engine   
 

  
 
 
 
 

 
Change By: 
 David McTavish  
 
 
Priority: 
 Normal Low  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-4966) Auto-update clj-parent in puppetdb and pe ext

2022-02-10 Thread David McTavish (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David McTavish updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4966  
 
 
  Auto-update clj-parent in puppetdb and pe ext   
 

  
 
 
 
 

 
Change By: 
 David McTavish  
 
 
Priority: 
 Normal Low  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-5342) Fix catalog validation "crutch"

2022-02-10 Thread David McTavish (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David McTavish updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-5342  
 
 
  Fix catalog validation "crutch"   
 

  
 
 
 
 

 
Change By: 
 David McTavish  
 
 
Priority: 
 Normal Low  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-4937) Add a default statement timeout to user queries

2022-02-10 Thread David McTavish (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David McTavish updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4937  
 
 
  Add a default statement timeout to user queries   
 

  
 
 
 
 

 
Change By: 
 David McTavish  
 
 
Priority: 
 Normal Low  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-4937) Add a default statement timeout to user queries

2022-02-10 Thread David McTavish (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David McTavish updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4937  
 
 
  Add a default statement timeout to user queries   
 

  
 
 
 
 

 
Change By: 
 David McTavish  
 
 
Story Points: 
 5  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-5352) Re-allow branched migrations

2022-02-10 Thread David McTavish (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David McTavish updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-5352  
 
 
  Re-allow branched migrations   
 

  
 
 
 
 

 
Change By: 
 David McTavish  
 
 
Priority: 
 Normal Low  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-4987) Ruby 2.7 Warnings after Upgrade to PuppetDB 7

2022-02-10 Thread David McTavish (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David McTavish updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4987  
 
 
  Ruby 2.7 Warnings after Upgrade to PuppetDB 7   
 

  
 
 
 
 

 
Change By: 
 David McTavish  
 
 
Priority: 
 Normal Low  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-5162) Accept wildcard `*` for PDB API endpoints

2022-02-10 Thread David McTavish (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David McTavish updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-5162  
 
 
  Accept wildcard `*` for PDB API endpoints   
 

  
 
 
 
 

 
Change By: 
 David McTavish  
 
 
Priority: 
 Normal Low  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-4967) Use the jenkins tag job

2022-02-10 Thread David McTavish (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David McTavish updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4967  
 
 
  Use the jenkins tag job   
 

  
 
 
 
 

 
Change By: 
 David McTavish  
 
 
Priority: 
 Normal Low  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-4763) Document command broadcast

2022-02-10 Thread David McTavish (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David McTavish updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4763  
 
 
  Document command broadcast   
 

  
 
 
 
 

 
Change By: 
 David McTavish  
 
 
Sprint: 
 HA 2022-02-16  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-4763) Document command broadcast

2022-02-10 Thread David McTavish (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David McTavish updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4763  
 
 
  Document command broadcast   
 

  
 
 
 
 

 
Change By: 
 David McTavish  
 
 
Labels: 
 low-hanging-fruit  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-5085) Support for installing puppetdb and puppetserver on same system

2022-02-10 Thread David McTavish (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David McTavish updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-5085  
 
 
  Support for installing puppetdb and puppetserver on same system   
 

  
 
 
 
 

 
Change By: 
 David McTavish  
 
 
Priority: 
 Normal Low  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-5085) Support for installing puppetdb and puppetserver on same system

2022-02-10 Thread David McTavish (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David McTavish updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-5085  
 
 
  Support for installing puppetdb and puppetserver on same system   
 

  
 
 
 
 

 
Change By: 
 David McTavish  
 
 
Summary: 
 Support for installing puppetdb  module break  and  puppetserver  when both are installed  on same  machine  system  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-5085) puppetdb module break puppetserver when both are installed on same machine

2022-02-10 Thread David McTavish (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David McTavish updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-5085  
 
 
  puppetdb module break puppetserver when both are installed on same machine   
 

  
 
 
 
 

 
Change By: 
 David McTavish  
 
 
Method Found: 
 Needs Assessment  
 
 
Issue Type: 
 Bug Story  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-5085) puppetdb module break puppetserver when both are installed on same machine

2022-02-10 Thread David McTavish (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David McTavish updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-5085  
 
 
  puppetdb module break puppetserver when both are installed on same machine   
 

  
 
 
 
 

 
Change By: 
 David McTavish  
 
 
Labels: 
 has_workaround  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-5062) Remove password entry from database.ini when using certificate authentication

2022-02-10 Thread David McTavish (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David McTavish updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-5062  
 
 
  Remove password entry from database.ini when using certificate authentication   
 

  
 
 
 
 

 
Change By: 
 David McTavish  
 
 
Priority: 
 Normal Low  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-5278) Grouping by a fact with a / in the name generates 500

2022-02-10 Thread David McTavish (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David McTavish updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-5278  
 
 
  Grouping by a fact with a / in the name generates 500   
 

  
 
 
 
 

 
Change By: 
 David McTavish  
 
 
Sprint: 
 HA 2021-09-22, HA 2021-10-06, HA 2021-10-20, HA 2021-11-03, HA 2021-11-17, HA 2021-12-01, HA 2021-12-15 , HA 2022-03-02  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-5278) Grouping by a fact with a / in the name generates 500

2022-02-10 Thread David McTavish (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David McTavish updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-5278  
 
 
  Grouping by a fact with a / in the name generates 500   
 

  
 
 
 
 

 
Change By: 
 David McTavish  
 
 
Story Points: 
 2  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-5278) Grouping by a fact with a / in the name generates 500

2022-02-10 Thread David McTavish (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David McTavish updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-5278  
 
 
  Grouping by a fact with a / in the name generates 500   
 

  
 
 
 
 

 
Change By: 
 David McTavish  
 
 
Priority: 
 Normal Major  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-5278) Grouping by a fact with a / in the name generates 500

2022-02-10 Thread David McTavish (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David McTavish assigned an issue to Austin Blatt  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-5278  
 
 
  Grouping by a fact with a / in the name generates 500   
 

  
 
 
 
 

 
Change By: 
 David McTavish  
 
 
Assignee: 
 Austin Blatt  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-5278) Grouping by a fact with a / in the name generates 500

2022-02-10 Thread David McTavish (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David McTavish assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-5278  
 
 
  Grouping by a fact with a / in the name generates 500   
 

  
 
 
 
 

 
Change By: 
 David McTavish  
 
 
Assignee: 
 Austin Blatt  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-5379) Invalid option clientcert=1 with Postgres 14

2022-02-10 Thread David McTavish (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David McTavish updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-5379  
 
 
  Invalid option clientcert=1 with Postgres 14   
 

  
 
 
 
 

 
Change By: 
 David McTavish  
 
 
Labels: 
 low-hanging-fruit  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-5379) Invalid option clientcert=1 with Postgres 14

2022-02-10 Thread David McTavish (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David McTavish updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-5379  
 
 
  Invalid option clientcert=1 with Postgres 14   
 

  
 
 
 
 

 
Change By: 
 David McTavish  
 
 
Sprint: 
 HA 2022-03-02 HAHA On Deck  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-5379) Invalid option clientcert=1 with Postgres 14

2022-02-10 Thread David McTavish (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David McTavish updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-5379  
 
 
  Invalid option clientcert=1 with Postgres 14   
 

  
 
 
 
 

 
Change By: 
 David McTavish  
 
 
Sprint: 
 HA 2022-03-02  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-5379) Invalid option clientcert=1 with Postgres 14

2022-02-10 Thread David McTavish (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David McTavish updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-5379  
 
 
  Invalid option clientcert=1 with Postgres 14   
 

  
 
 
 
 

 
Change By: 
 David McTavish  
 
 
Epic Link: 
 PE-32590  
 

  
 
 
 
 

 
 
 

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


Jira (PUP-11454) Cannot login under user created by Puppet on MacOS 12.1

2022-02-10 Thread Dmitriy Grigorev (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dmitriy Grigorev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-11454  
 
 
  Cannot login under user created by Puppet on MacOS 12.1   
 

  
 
 
 
 

 
Change By: 
 Dmitriy Grigorev  
 
 
Environment: 
 System:  {code} uname -prsvDarwin 21.2.0 Darwin Kernel Version 21.2.0: Sun Nov 28 20:28:54 PST 2021; root:xnu-8019.61.5~1/RELEASE_X86_64 i386{code}Puppet:{code}puppet --version7.14.0{code}  
 

  
 
 
 
 

 
 
 

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


Jira (PUP-11454) Cannot login under user created by Puppet on MacOS 12.1

2022-02-10 Thread Dmitriy Grigorev (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dmitriy Grigorev created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-11454  
 
 
  Cannot login under user created by Puppet on MacOS 12.1   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 PUP 7.14.0  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2022/02/10 3:52 AM  
 
 
Environment: 
 System:  
 
 
 
 
  uname -prsv  
 
 
 Darwin 21.2.0 Darwin Kernel Version 21.2.0: Sun Nov 28 20:28:54 PST 2021; root:xnu-8019.61.5~1/RELEASE_X86_64 i386
  
 
 
 
  Puppet:  
 
 
 
 
 puppet --version  
 
 
 7.14.0
  
 
 
 
   
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Dmitriy Grigorev  
 

  
 

Jira (PUP-11454) Cannot login under user created by Puppet on MacOS 12.1

2022-02-10 Thread Dmitriy Grigorev (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dmitriy Grigorev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-11454  
 
 
  Cannot login under user created by Puppet on MacOS 12.1   
 

  
 
 
 
 

 
Change By: 
 Dmitriy Grigorev  
 

  
 
 
 
 

 
 I create a new user using code example from  stdlib docs {code}$pw = Sensitive.new('Pa55w0rd')$salt = Sensitive.new('Using s0m3 s@lt')$pw_info = Sensitive.new(str2saltedpbkdf2($pw, $salt, 5))user { 'jdoe':  ensure => present,  iterations => unwrap($pw_info)['interations'],  password   => unwrap($pw_info)['password_hex'],  salt   => unwrap($pw_info)['salt_hex'],}{code}Everything applies with no error, but I can't login until I change password via system preferences.System:{code} uname -prsvDarwin 21.2.0 Darwin Kernel Version 21.2.0: Sun Nov 28 20:28:54 PST 2021; root:xnu-8019.61.5~1/RELEASE_X86_64 i386{code}Puppet:{code}puppet --version7.14.0{code}  
 

  
 
 
 
 

 
 
 

 
 
 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 

Jira (PUP-11440) No option to fail fast when agent-specified environment does not exist

2022-02-10 Thread Josh Cooper (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  PUP-11440  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: No option to fail fast when agent-specified environment does not exist   
 

  
 
 
 
 

 
 In the non-strict mode case, we do want the agent run to continue and have the server redirect the agent to a valid environment. Otherwise, if you've configured all 50k agents to use a specific environment and you delete the environment from the server, then all agents will be stuck and you can't use puppet to fix itself. In the strict mode case, if we detect that the environment doesn't exist on the server prior to pluginsync, then we should abort the run, since we know there's no point in continuing. This seems to work as expected:  
 
 
 
 
 diff --git a/lib/puppet/configurer.rb b/lib/puppet/configurer.rb  
 
 
 index d97c73bc46..457b9eed8e 100644  
 
 
 --- a/lib/puppet/configurer.rb  
 
 
 +++ b/lib/puppet/configurer.rb  
 
 
 @@ -327,12 +327,16 @@ class Puppet::Configurer  
 
 
  push_current_environment_and_loaders  
 
 
end  
 
 

 
 
 +  # store original value so it can be restored later  
 
 
temp_value = options[:pluginsync]