Jira (PUP-8088) add mechanism for cache eviction callback / finalizers
Title: Message Title Josh Cooper commented on PUP-8088 Re: add mechanism for cache eviction callback / finalizers I think the connection handling use case is better handled by using the connection pooling built into puppet and puppetserver. It's possible this is still needed when using a 3rd party sdk/gem that has its own connection handling logic, and the function needs to cache the connection across requests, so I'm going to put this in needs information. 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.218549.150892772.86604.1592010360022%40Atlassian.JIRA.
Jira (PUP-10253) Undeprecate source_permissions
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10253 Undeprecate source_permissions Change By: Josh Cooper Sprint: Coremunity Grooming Hopper 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.343626.1579985788000.86603.1592010240026%40Atlassian.JIRA.
Jira (PUP-6380) HTTP file sources fail for GET-only URIs
Title: Message Title Josh Cooper updated an issue Puppet / PUP-6380 HTTP file sources fail for GET-only URIs Change By: Josh Cooper Sprint: Coremunity Hopper 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.135135.1464891665000.86602.1592010180199%40Atlassian.JIRA.
Jira (PUP-6114) Add support for Artifactory checksum headers and enable SHA1 checksum type
Title: Message Title Josh Cooper updated an issue Puppet / PUP-6114 Add support for Artifactory checksum headers and enable SHA1 checksum type Change By: Josh Cooper Sprint: Coremunity Hopper 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.124334.1459384692000.86599.1592010180056%40Atlassian.JIRA.
Jira (PUP-6916) Add support for username:password@domain for http/https sources
Title: Message Title Josh Cooper updated an issue Puppet / PUP-6916 Add support for username:password@domain for http/https sources Change By: Josh Cooper Sprint: Coremunity Hopper 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.160802.1479116725000.86600.1592010180111%40Atlassian.JIRA.
Jira (PUP-10368) Checksums not validated when downloading file http(s):// sources
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10368 Checksums not validated when downloading file http(s):// sources Change By: Josh Cooper Sprint: Coremunity Hopper 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.349628.1584115737000.86601.1592010180155%40Atlassian.JIRA.
Jira (PUP-8922) Look at the permissions of files in /cache/state/
Title: Message Title Josh Cooper commented on PUP-8922 Re: Look at the permissions of files in /cache/state/ Merged to 5.5.x in https://github.com/puppetlabs/puppet/commit/8c6758aa78a11066d01269dc69798a0a449236cc 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.259990.1528709944000.86588.1592007600045%40Atlassian.JIRA.
Jira (PUP-8922) Look at the permissions of files in /cache/state/
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8922 Look at the permissions of files in /cache/state/ Change By: Josh Cooper Fix Version/s: PUP 6.17.0 Fix Version/s: PUP 5.5.21 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.259990.1528709944000.86589.1592007600087%40Atlassian.JIRA.
Jira (PUP-10511) Sensitive data type is lost when declaring multiple resources using title arrays
Title: Message Title Josh Cooper commented on PUP-10511 Re: Sensitive data type is lost when declaring multiple resources using title arrays Ciprian Badescu could you add release notes? 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.358908.1589483014000.86583.1592007360075%40Atlassian.JIRA.
Jira (PUP-10511) Sensitive data type is lost when declaring multiple resources using title arrays
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10511 Sensitive data type is lost when declaring multiple resources using title arrays Change By: Josh Cooper Fix Version/s: PUP 6.17.0 Fix Version/s: PUP 5.5.21 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.358908.1589483014000.86580.1592007300088%40Atlassian.JIRA.
Jira (PUP-10511) Sensitive data type is lost when declaring multiple resources using title arrays
Title: Message Title Josh Cooper commented on PUP-10511 Re: Sensitive data type is lost when declaring multiple resources using title arrays Merged to 5.5.x in https://github.com/puppetlabs/puppet/commit/bfe98132bc83ce9718d2cb74325160655ed7f9fd. 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.358908.1589483014000.86581.1592007300137%40Atlassian.JIRA.
Jira (PUP-9252) injection of PAL compiler in 4.x function does not work when not invoked by PAL
Title: Message Title Josh Cooper commented on PUP-9252 Re: injection of PAL compiler in 4.x function does not work when not invoked by PAL The eval PR was declined, resetting this ticket status. 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.281367.153994484.86402.1591995000180%40Atlassian.JIRA.
Jira (PUP-9254) Agent Functions - add eval() function
Title: Message Title Josh Cooper commented on PUP-9254 Re: Agent Functions - add eval() function The eval PR was declined, resetting this ticket status. 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.281386.1539958926000.86403.1591995000223%40Atlassian.JIRA.
Jira (PUP-8971) Agent Functions - Add encrypt/decrypt functions
Title: Message Title Josh Cooper commented on PUP-8971 Re: Agent Functions - Add encrypt/decrypt functions The PR needed more work before it could be merged and was closed. I'm changing this ticket status to reflect reality. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.263096.1530205428000.86394.1591994880123%40Atlassian.JIRA.
Jira (PUP-9255) PAL - add the ability to evaluate logic in a nested local scope
Title: Message Title Josh Cooper commented on PUP-9255 Re: PAL - add the ability to evaluate logic in a nested local scope The eval PR was declined, resetting this ticket status. 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.281387.1539959106000.86391.1591994820676%40Atlassian.JIRA.
Jira (PUP-10536) Puppet windows package provider fails if there are garbage characters after an embedded NULL
Title: Message Title Austin Boyd updated an issue Puppet / PUP-10536 Puppet windows package provider fails if there are garbage characters after an embedded NULL Change By: Austin Boyd Zendesk Ticket Count: 1 2 Zendesk Ticket IDs: 38573 ,39469 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.360365.1590695652000.86291.1591991340032%40Atlassian.JIRA.
Jira (PUP-10536) Puppet windows package provider fails if there are garbage characters after an embedded NULL
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10536 Puppet windows package provider fails if there are garbage characters after an embedded NULL Change By: Josh Cooper Fix Version/s: PUP 6.17.0 Fix Version/s: PUP 5.5.21 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.360365.1590695652000.86101.1591983840031%40Atlassian.JIRA.
Jira (PUP-9251) Deprecate 'application orchestration' features
Title: Message Title Melissa Amos updated an issue Puppet / PUP-9251 Deprecate 'application orchestration' features Change By: Melissa Amos Labels: mamos-followup 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.281366.1539943536000.86015.1591979820319%40Atlassian.JIRA.
Jira (PUP-9251) Deprecate 'application orchestration' features
Title: Message Title Melissa Amos commented on PUP-9251 Re: Deprecate 'application orchestration' features Josh Cooper A couple of questions: Are the fix versions on this ticket correct? 5.5.21 and 6.17 don't correspond to any current or upcoming PE versions. (According to PE build info, 2018.1.16 has 5.5.20, and 2019.8 has 6.16.) Are we deprecating app orchestration in 2018.1, or only deprecating the related terminology? It's a little weird that the 2018.1 docs have an end-of-support warning for 2019.0, a later version. If we're essentially backporting the deprecation, I'll update the version in the warning note here. No separate DOCs ticket is needed on my part. I do wonder if there's a corresponding PE ticket for this, though? Seems like there might be some work on the PE side to implement this deprecation... The managing applications docs are 404ing in /latest because that feature was removed in a prior version. You have to change /latest to 2019.0 or earlier to see those docs. 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.281366.1539943536000.86008.159197976017
Jira (PDB-4760) Broadcast commands transiently fail with "Connection is closed"
Title: Message Title Rob Browning commented on PDB-4760 Re: Broadcast commands transiently fail with "Connection is closed" After some investigation, it looks like the underlying cause was the fact that in the initial, somewhat hurried version of the broadcast code, I added a db connection "with" wrapper around the call-with-quick-retry loop, and that loop suppresses exceptions, so that wen there was (for example) a serialization failure, instead of getting a new connection for the next attempt, the (new) top-level wrapper would cause us to continue to use the existing connection, the one we were using when we hit the error. That's because the with connection forms nest, and only the topmost "with connection" wrapper will actually close a connection. We suspected that continuing to use the connection after the failure might be what was causing the closed connection exceptions. To test that, I added some code to exec-replace-facts to force all calls to block just before the storage work, and just after, along with some flushed console output to document the ordering, all within the exec-replace-facts transaction. Then I annotated call-with-quick-retry to refresh the connection's information via (.isValid connection 0) and print (.isClosed connection) whenever an exception is thrown by an attempt (.isClosed may not be accurate without the .isValid refresh). Finally, I added two identical facts to the queue (to ensure competing deliveries) and started PuppetDB with broadcast enabled. Upon startup the output indicated that PuppetDB attempted concurrent delivery of the duplicate facts, provoking a "could not serialize access due to concurrent update" exception, followed by diagnostic output indicating that the connection was closed. After that the "closed connection" exception was thrown, supporting the initial hypothesis. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-9251) Deprecate 'application orchestration' features
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9251 Deprecate 'application orchestration' features Change By: Josh Cooper Component/s: Docs 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.281366.1539943536000.85827.1591973760108%40Atlassian.JIRA.
Jira (PUP-9251) Deprecate 'application orchestration' features
Title: Message Title Josh Cooper commented on PUP-9251 Re: Deprecate 'application orchestration' features Merged to 5.5.x in https://github.com/puppetlabs/puppet/commit/4f5bd15e777cd55fb0dafacec54da7fceb4ac1a3 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.281366.1539943536000.85828.1591973760259%40Atlassian.JIRA.
Jira (PUP-9251) Deprecate 'application orchestration' features
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9251 Deprecate 'application orchestration' features Change By: Josh Cooper Fix Version/s: PUP 5.5.21 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.281366.1539943536000.85826.1591973760051%40Atlassian.JIRA.
Jira (PUP-5758) Remove usage of win32-service gem (if applicable)
Title: Message Title Gabriel Nagy assigned an issue to Gabriel Nagy Puppet / PUP-5758 Remove usage of win32-service gem (if applicable) Change By: Gabriel Nagy Assignee: Gabriel Nagy 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.114064.1453854223000.85787.1591965000288%40Atlassian.JIRA.
Jira (PUP-9505) Fact yaml should quote mac addresses.
Title: Message Title Bogdan Irimie updated an issue Puppet / PUP-9505 Fact yaml should quote mac addresses. Change By: Bogdan Irimie Attachment: puppet_facts__render_as_yaml Attachment: facter4_yaml_with_numbers Attachment: facter4_yaml_with_letters 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.296813.1550680699000.85744.1591955100040%40Atlassian.JIRA.
