Jira (PUP-10547) Manage user rights on Windows
Title: Message Title Luchian Nemes assigned an issue to Luchian Nemes Puppet / PUP-10547 Manage user rights on Windows Change By: Luchian Nemes Assignee: Luchian Nemes Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.363693.1592980666000.96020.1593155880032%40Atlassian.JIRA.
Jira (FACT-2682) facter -p returns NUL character on stdout when called from nested ruby on windows
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2682 facter -p returns NUL character on stdout when called from nested ruby on windows Change By: Mihai Buzgau Sprint: PR NW - Triage 2020-07-08 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.363822.1593026104000.96022.1593157320095%40Atlassian.JIRA.
Jira (FACT-2682) facter -p returns NUL character on stdout when called from nested ruby on windows
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2682 facter -p returns NUL character on stdout when called from nested ruby on windows Change By: Mihai Buzgau Story Points: 2 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.363822.1593026104000.96021.1593157320041%40Atlassian.JIRA.
Jira (FACT-2218) virtual fact for OSX
Title: Message Title Bogdan Irimie commented on FACT-2218 Re: virtual fact for OSX facter -v 3.14.11 (commit ed6c9052b125bee55f21f43d55f790c08ec75c1c) facter virtual parallels ./bin/facter -v 4.0.28 ./bin/facter virtual parallels
Jira (PUP-9370) Could not evaluate: ADSI connection error: failed to parse display name
Title: Message Title Nick Howell commented on PUP-9370 Re: Could not evaluate: ADSI connection error: failed to parse display name Another +1 on this. I see the same error that Paul and Aaron mention. Interestingly, if I manually create the local user via Computer Management, Puppet is then able to manage it as expected. 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.289482.154525563.96241.1593178080022%40Atlassian.JIRA.
Jira (PUP-9819) Puppet Failure on MacOS 10.15 'Catalina' Beta3
Title: Message Title Josh Cooper commented on PUP-9819 Re: Puppet Failure on MacOS 10.15 'Catalina' Beta3 Marshall Taylor could you try a more recent version of puppet-agent and see if the issue is resolved? 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.316143.1562866804000.96487.1593190200139%40Atlassian.JIRA.
Jira (PUP-9819) Puppet Failure on MacOS 10.15 'Catalina' Beta3
Title: Message Title Josh Cooper assigned an issue to Marshall Taylor Puppet / PUP-9819 Puppet Failure on MacOS 10.15 'Catalina' Beta3 Change By: Josh Cooper Assignee: Marshall Taylor 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.316143.1562866804000.96488.1593190200184%40Atlassian.JIRA.
Jira (PUP-10549) HTTP 406 Not Acceptable error message should contain format names
Title: Message Title Josh Cooper created an issue Puppet / PUP-10549 HTTP 406 Not Acceptable error message should contain format names Issue Type: Bug Assignee: Unassigned Created: 2020/06/26 9:54 AM Priority: Normal Reporter: Josh Cooper If the server can't generate a response in a mime type that the agent accepts, the server will emit an HTTP 406 Not Acceptable error, but the message includes the format objects instead of the names, leading to an unintelligible message on the agent: Warning: Error 406 on SERVER: Not Acceptable: No supported formats are acceptable (Accept: [#, @charset=#, @render_multiple_method="to_multiple_json", @extension="json", @intern_multiple_method="from_multiple_json", @render_method="to_json", @weight=15, @mime="application/json", @intern_method=:from_data_hash, @options=nil>, #, @charset=nil, @render_multiple_method="to_multiple_pson", @extension="pson", @intern_multiple_method="from_multiple_pson", @render_method="to_pson", @weight=10, @mime="text/pson", @intern_method=:from_data_hash, @options=nil>])
Jira (PUP-10549) HTTP 406 Not Acceptable error message should contain format names
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10549 HTTP 406 Not Acceptable error message should contain format names Change By: Josh Cooper Team: Coremunity 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.364176.1593190474000.96625.1593196860081%40Atlassian.JIRA.
Jira (PUP-10549) HTTP 406 Not Acceptable error message should contain format names
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10549 HTTP 406 Not Acceptable error message should contain format names 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.364176.1593190474000.96624.1593196860064%40Atlassian.JIRA.
Jira (PUP-10549) HTTP 406 Not Acceptable error message should contain format names
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10549 HTTP 406 Not Acceptable error message should contain format names Change By: Josh Cooper Release Notes: Bug Fix Release Notes Summary: Print the names of the unacceptable network formats, not the format objects. 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.364176.1593190474000.96626.1593196860123%40Atlassian.JIRA.
Jira (PUP-10549) HTTP 406 Not Acceptable error message should contain format names
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10549 HTTP 406 Not Acceptable error message should contain format names Change By: Josh Cooper Sprint: Platform Core KANBAN 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.364176.1593190474000.96630.1593196980024%40Atlassian.JIRA.
Jira (PUP-9644) Improve documentation around sensitive data in puppet
Title: Message Title Jean Bond commented on PUP-9644 Re: Improve documentation around sensitive data in puppet We just got some user feedback about these docs, so I'm adding the request here for context: "Add a proper example to use in a class. When you define a var as Sensitive[String], you get the error "parameter 'X' expects a Sensitive[String] value, got String". When following the docs it is unclear how to properly configure this." 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.304741.1555347266000.96702.1593202500041%40Atlassian.JIRA.
Jira (PUP-6916) Add support for username:password@domain for http/https sources
Title: Message Title Josh Cooper commented on PUP-6916 Re: Add support for username:password@domain for http/https sources Passed CI in 392353374d3585b51909dc3cd7cbd18ccc8d61d4 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.96810.1593207720226%40Atlassian.JIRA.
Jira (PUP-9971) Add ETag support to the source attribute of the file resource type for http
Title: Message Title Josh Cooper commented on PUP-9971 Re: Add ETag support to the source attribute of the file resource type for http If he desired checksum type and value are specified in the manifest, which is fairly common, then the need for ETag goes away. So I’m going to close this as won’t do. 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.321721.1566385045000.96814.1593208020083%40Atlassian.JIRA.