Jira (PUP-9960) Puppet::Util::Execution.execute('command') does not return a Puppet::ExecutionFailure on Windows
Title: Message Title
Trevor Vaughan created an issue
Puppet / PUP-9960
Puppet::Util::Execution.execute('command') does not return a Puppet::ExecutionFailure on Windows
Issue Type:
Bug
Affects Versions:
PUP 5.5.16
Assignee:
Henrik Lindberg
Components:
Functions, Windows
Created:
2019/08/12 6:40 PM
Priority:
Normal
Reporter:
Trevor Vaughan
Puppet Version: 5.5.16 Puppet Server Version: N/A OS Name/Version: Windows 2012r2 Running Puppet::Util::Execution.execute('foo') should raise a Puppet::ExecutionFailure exception but, instead raises Errno::ENOENT since the command is not found. This appears to go against the documented API of the function and makes creating code that is safe for all operating systems difficult. Desired Behavior: Always raise Puppet::ExecutionFailure on an error. Actual Behavior: Errno::ENOENT is raised.
Add Comment
Jira (PUP-8662) puppet plugin download doesn't re-use HTTP connections
Title: Message Title Josh Cooper commented on PUP-8662 Re: puppet plugin download doesn't re-use HTTP connections The networking and ssl code is fragile prior to 6.4, so for those versions I've added a simple patch to fix puppet plugin download specifically. I'll file a separate ticket to delete the non-caching pool to avoid this kind of problem in the future, and same with the puppet device command. The reason I couldn't do that earlier, is we have to be careful about reusing connections with different SSL context/trust stores, and that's not possible in the older code. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.245716.1523666018000.52861.1565655960173%40Atlassian.JIRA.
Jira (PUP-8662) puppet plugin download doesn't re-use HTTP connections
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8662 puppet plugin download doesn't re-use HTTP connections Change By: Josh Cooper Fix Version/s: PUP 6.4.4 Fix Version/s: PUP 6.0.11 Fix Version/s: PUP 5.5.17 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.245716.1523666018000.52853.1565655841099%40Atlassian.JIRA.
Jira (PDOC-277) Ensure that multiline examples are correctly parsed
Title: Message Title Jean Bond assigned an issue to Jean Bond Puppet Strings / PDOC-277 Ensure that multiline examples are correctly parsed Change By: Jean Bond Assignee: Jean Bond Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.307014.1556751181000.52819.1565655600824%40Atlassian.JIRA.
Jira (PDOC-277) Ensure that multiline examples are correctly parsed
Title: Message Title
Jean Bond updated an issue
Puppet Strings / PDOC-277
Ensure that multiline examples are correctly parsed
Change By:
Jean Bond
Comment:
The spacing on the above example has been fixed, but still has issues. I also found an issue with this line in functions:For example, in the `break` function (starting at line 1):{code}# Breaks an innermost iteration as if it encountered an end of input.# This function does not return to the caller.## The signal produced to stop the iteration bubbles up through# the call stack until either terminating the innermost iteration or# raising an error if the end of the call stack is reached.## The break() function does not accept an argument.## @example Using `break`## ```puppet# $data = ""># notice $data.map |$x| { if $x == 3 { break() } $x*10 }# ```## Would notice the value `[10, 20]`{code}renders in generated docs output as {code}Breaks an innermost iteration as if it encountered an end of input.This function does not return to the caller.The signal produced to stop the iteration bubbles up throughthe call stack until either terminating the innermost iteration orraising an error if the end of the call stack is reached.The break() function does not accept an argument.```puppet$data = "">notice $data.map |$x| { if $x == 3 { break() } $x*10 }```Would notice the value `[10, 20]`{code}
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDOC-277) Ensure that multiline examples are correctly parsed
Title: Message Title Jean Bond commented on PDOC-277 Re: Ensure that multiline examples are correctly parsed It's possible the issue here is in the docs tooling rather than in Strings. I'll investigate this as far as I can, but I may wind up looking for help on it. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.307014.1556751181000.52815.1565655540375%40Atlassian.JIRA.
Jira (PDOC-277) Ensure that multiline examples are correctly parsed
Title: Message Title Jean Bond updated an issue Puppet Strings / PDOC-277 Ensure that multiline examples are correctly parsed Change By: Jean Bond Labels: generated-docs Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.307014.1556751181000.52754.1565653200355%40Atlassian.JIRA.
Jira (PDOC-277) Ensure that multiline examples are correctly parsed
Title: Message Title Jean Bond commented on PDOC-277 Re: Ensure that multiline examples are correctly parsed The spacing on the above example has been fixed, but still has issues. I also found an issue with this line in functions: For example, in the `break` function (starting at line 1): # Breaks an innermost iteration as if it encountered an end of input. # This function does not return to the caller. # # The signal produced to stop the iteration bubbles up through # the call stack until either terminating the innermost iteration or # raising an error if the end of the call stack is reached. # # The break() function does not accept an argument. # # @example Using `break` # # ```puppet # $data = "">
Jira (BOLT-1384) Inventory command
Title: Message Title Alex Dreyer commented on BOLT-1384 Re: Inventory command I don't think just removing the final line is a good long term solution. We intended to solve multiple use cases with the fix we added one of which was predicting what target a bolt command would run on. In that case the count is useful. In general the default "human" output for bolt is not intended to be stable for consumption from bash scripts which is why we've discussed a "oneline" format in the past. If we do add oneline support for this feature we should make sure to add some information beyond the 'name' to force the user to use cut in the initial release otherwise we'll likely break the output in the future. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.312167.1560296026000.52730.1565651700226%40Atlassian.JIRA.
Jira (PUP-8662) puppet plugin download doesn't re-use HTTP connections
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-8662 puppet plugin download doesn't re-use HTTP connections Change By: Josh Cooper Assignee: Josh Cooper Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.245716.1523666018000.52713.1565651160913%40Atlassian.JIRA.
Jira (PUP-8662) puppet plugin download doesn't re-use HTTP connections
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8662 puppet plugin download doesn't re-use HTTP connections Change By: Josh Cooper Sprint: Platform Core KANBAN Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.245716.1523666018000.52715.1565651160926%40Atlassian.JIRA.
Jira (BOLT-1384) Inventory command
Title: Message Title
Corey Osman commented on BOLT-1384
Re: Inventory command
IMHO, the default usage of this command will be for scripts. If that is the case we should make the default behavior work for the scripts and not against them. So in a case like:
#!/usr/bin/env bash nodes=$(bolt inventory --nodes ubuntu) for node in $nodes; do ssh-copy-id ethos@${nodes} done
I don't want to go hunt down which modifier I need to add in order to not return "55 targets". I also don't want to run the command first only to have it fail on the node called "55" and "targets". So I would like to have this count removed by default.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit
Jira (PUP-9957) puppet apply command fails when external modules are installed
Title: Message Title Henrik Lindberg commented on PUP-9957 Re: puppet apply command fails when external modules are installed Hm, this seems familiar. We had issues that were caused by logic using an old style of resource initialization that caused a resource type to be loaded only in the old way, then when the new "right way" of loading is used it trips over the load that snuck under the radar. I think this could be PUP-8002 or PDB-3734 or a similar problem in another location. I don't think the checking of declarations in the wrong place would cause this problem - if that was they case there would be a specific error, or if such problems were present that those checks prevent that they would cause leakage between contexts (i.e. causing monkey patching at worst). Looking at the line in question that is reported as being in error is the init.pp of stdlib where the class stdlib is defined - it in turn includes definitions of additional stages. This leads me to suspect that something is going on inside the Stage datatype (maybe an "old style initialization" that has gone unnoticed. In any case, worth trying to reproduce under Puppet 6. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.313933.1561476226000.52659.1565650320206%40Atlassian.JIRA.
Jira (PUP-9043) Downloaded files are sometimes truncated
Title: Message Title Josh Cooper commented on PUP-9043 Re: Downloaded files are sometimes truncated I confirmed the ruby behavior is definitely incorrect, from https://tools.ietf.org/html/rfc7230#section-3.4 A message that uses a valid Content-Length is incomplete if the size of the message body received (in octets) is less than the value given by Content-Length. I'm going to patch our vendored ruby and push on getting the ruby PR merged upstream. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.268200.1533583523000.52597.1565649180724%40Atlassian.JIRA.
Jira (BOLT-1384) Inventory command
Title: Message Title Alex Dreyer commented on BOLT-1384 Re: Inventory command This seems like a usecase for the often discussed `--format oneline` Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.312167.1560296026000.52590.1565649120314%40Atlassian.JIRA.
Jira (PUP-9732) Client should cache successful host address for at least the length of a Puppet run
Title: Message Title Josh Cooper commented on PUP-9732 Re: Client should cache successful host address for at least the length of a Puppet run The current agent behavior may be good enough here, because it uses persistent HTTP connections. So during a normal agent run, it will try to reuse the same TCP connection. If the connection is idle, such as due to a long running exec, package install, etc, then the agent will timeout the idle connection and create a new one, retriggering the lookup. But that's more of the exception than the rule. If we need to do something more than that, then we probably want to handle the DNS resolution ourselves via Resolv::DNS and store the resolved IP address for the run. However, we'll have to do some extra work to handle the certname mismatch since the IP we tried to connect to doesn't match the server's certname. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.311676.1559921066000.52555.1565648460112%40Atlassian.JIRA.
Jira (PUP-2172) Don't use an http proxy when connecting to localhost
Title: Message Title Josh Cooper commented on PUP-2172 Re: Don't use an http proxy when connecting to localhost Merged to 5.5.x in https://github.com/puppetlabs/puppet/commit/e8d183a7774677331632dbbb6b83a51ca49b07d9 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.31144.1396893516000.52549.1565648280380%40Atlassian.JIRA.
Jira (PUP-4470) Puppet's http connection factory doesn't support authenticating proxies
Title: Message Title Josh Cooper commented on PUP-4470 Re: Puppet's http connection factory doesn't support authenticating proxies Merged to 5.5.x in https://github.com/puppetlabs/puppet/commit/2e44ab5e113c9417d9a4ae4d83043cd09e642432 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.77763.1430247156000.52550.1565648280385%40Atlassian.JIRA.
Jira (PDB-4479) Deactivate node commands sync after garbage collection
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-4479 Deactivate node commands sync after garbage collection Issue Type: Bug Assignee: Unassigned Created: 2019/08/12 3:13 PM Priority: Normal Reporter: Austin Blatt This is a bug in PE's HA sync. On the local PuppetDB, when a node is purged after a deactivate node command and then a garbage collection run after node-purge-ttl time has passed, the node is deleted. The remote PuppetDB also has that deactivated node present, but has not run garbage collection, when the local PuppetDB (that has just garbage collection the node) attempts to sync from the remote it will sync back the node it just garbage collected. This will result in a ping-pong effect and the node will never be purged from PuppetDB Add Comment
Jira (PDB-3300) Add command for deleting node data
Title: Message Title Travis Fields commented on PDB-3300 Re: Add command for deleting node data Any update on this ticket? It's been a bit long Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.176102.1487778838000.52444.1565646120584%40Atlassian.JIRA.
Jira (PDOC-274) Add provider attribute to docs output
Title: Message Title Jean Bond updated an issue Puppet Strings / PDOC-274 Add provider attribute to docs output Change By: Jean Bond Labels: generated-docs Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.295581.1549669062000.52417.1565645880168%40Atlassian.JIRA.
Jira (PDOC-66) Document whether resource types react to refresh events
Title: Message Title Jean Bond updated an issue Puppet Strings / PDOC-66 Document whether resource types react to refresh events Change By: Jean Bond Labels: generated-docs Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.103155.1446036354000.52405.1565645280260%40Atlassian.JIRA.
Jira (PDOC-66) Document whether resource types react to refresh events
Title: Message Title Jean Bond commented on PDOC-66 Re: Document whether resource types react to refresh events This would be a nice enhancement to the generated types documentation, but Eric Putnam's comment is still correct: nice to have, not a blocker or top priority. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.103155.1446036354000.52403.1565645280253%40Atlassian.JIRA.
Jira (PDOC-55) @!puppet.type.parameter (and property) directive should be able to add metadata
Title: Message Title Jean Bond updated an issue Puppet Strings / PDOC-55 @!puppet.type.parameter (and property) directive should be able to add metadata Change By: Jean Bond Labels: generated-docs Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.98669.1442597964000.52393.1565645100274%40Atlassian.JIRA.
Jira (PDOC-55) @!puppet.type.parameter (and property) directive should be able to add metadata
Title: Message Title Jean Bond commented on PDOC-55 Re: @!puppet.type.parameter (and property) directive should be able to add metadata Wow. I have no idea if we still need this or not. A lot of the core types have since been moved into modules, but given the types that we still have, maybe this is part of the issue with that output being inaccurate. Consult with Strings devs. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.98669.1442597964000.52391.1565645040091%40Atlassian.JIRA.
Jira (PDOC-96) Strings needs to document core puppet references (indirection, configuration, metaparameter, etc)
Title: Message Title
Jean Bond updated an issue
Puppet Strings / PDOC-96
Strings needs to document core puppet references (indirection, configuration, metaparameter, etc)
Change By:
Jean Bond
`puppet doc` provided a facility for creating reference docs from {{lib/puppet/reference}}. That includes the following:{code}[16:46:24] whopper:~/Coding/puppet ‹master*› » bundle exec puppet doc --listconfiguration - A reference for all settingsfunction - All functions available in the parserindirection - Indirection types and their terminus classesmetaparameter - All Puppet metaparameters and all their detailsproviders - Which providers are valid for this machinereport - All available transaction reportstype - All Puppet resource types and all their details{code}Strings currently handles functions, providers, and types. The others live at https://puppet.com/docs/puppet/latest/ (example, https://puppet.com/docs/puppet/latest/indirection.html) (link edited updated by Jean Bond 12 August 2019)Strings has never supported indirection, metaparameters, reports or configuration docs. The docs team will need these to be functional to populate the site.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDOC-96) Strings needs to document core puppet references (indirection, configuration, metaparameter, etc)
Title: Message Title Jean Bond commented on PDOC-96 Re: Strings needs to document core puppet references (indirection, configuration, metaparameter, etc) Update! Some of these generated docs no longer need to be generated, because: they are not useful for most users (indirection) they are stable docs and can be handled as more-or-less static docs (metaparameter, report) they aren't in the docs repo or recent docs memory at all (providers). The docs that we WOULD like Strings to handle are: *configuration: Strings does NOT generate this, and tech pubs would love for Strings to do this. function: Strings generates this, but may have some issues? I need to look at a diff, it might be fine actually. type: Strings generates this, but with numerous problems. * Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit
Jira (PDOC-96) Strings needs to document core puppet references (indirection, configuration, metaparameter, etc)
Title: Message Title
Jean Bond updated an issue
Puppet Strings / PDOC-96
Strings needs to document core puppet references (indirection, configuration, metaparameter, etc)
Change By:
Jean Bond
`puppet doc` provided a facility for creating reference docs from {{lib/puppet/reference}}. That includes the following:{code}[16:46:24] whopper:~/Coding/puppet ‹master*› » bundle exec puppet doc --listconfiguration - A reference for all settingsfunction - All functions available in the parserindirection - Indirection types and their terminus classesmetaparameter - All Puppet metaparameters and all their detailsproviders - Which providers are valid for this machinereport - All available transaction reportstype - All Puppet resource types and all their details{code}Strings currently handles functions, providers, and types. The others live at https://puppet.com/docs/puppet/latest/ (example, https://puppet.com/docs/puppet/latest/indirection.html) (link edited by Jean Bond 12 August 2019) Strings has never supported indirection, metaparameters, reports or configuration docs. The docs team will need these to be functional to populate the site.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDOC-96) Strings needs to document core puppet references (indirection, configuration, metaparameter, etc)
Title: Message Title
Jean Bond updated an issue
Puppet Strings / PDOC-96
Strings needs to document core puppet references (indirection, configuration, metaparameter, etc)
Change By:
Jean Bond
`puppet doc` provided a facility for creating reference docs from {{lib/puppet/reference}}. That includes the following:{code}[16:46:24] whopper:~/Coding/puppet ‹master*› » bundle exec puppet doc --listconfiguration - A reference for all settingsfunction - All functions available in the parserindirection - Indirection types and their terminus classesmetaparameter - All Puppet metaparameters and all their detailsproviders - Which providers are valid for this machinereport - All available transaction reportstype - All Puppet resource types and all their details{code}Strings currently handles functions, providers, and types. The others live at https:// docs. puppet.com/ docs/ puppet/latest/ reference (example, https:// docs. puppet.com/ docs/ puppet/latest/ reference/ indirection.html)Strings has never supported indirection, metaparameters, reports or configuration docs. The docs team will need these to be functional to populate the site.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDOC-96) Strings needs to document core puppet references (indirection, configuration, metaparameter, etc)
Title: Message Title Jean Bond updated an issue Puppet Strings / PDOC-96 Strings needs to document core puppet references (indirection, configuration, metaparameter, etc) Change By: Jean Bond Labels: generated-docs Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.152194.1473983529000.52331.1565644200218%40Atlassian.JIRA.
Jira (PUP-9959) Plugin sync to get latest fact set when running puppet facts upload
Title: Message Title Josh Cooper commented on PUP-9959 Re: Plugin sync to get latest fact set when running puppet facts upload No worries Tom Parker. The action is not currently documented, which would explain things. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.317346.1563668147000.52237.1565642160131%40Atlassian.JIRA.
Jira (PUP-9959) Plugin sync to get latest fact set when running puppet facts upload
Title: Message Title Josh Cooper moved an issue Puppet / PUP-9959 Plugin sync to get latest fact set when running puppet facts upload Change By: Josh Cooper Key: PA PUP - 2806 9959 Project: Puppet Agent Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.317346.1563668147000.52230.1565641860365%40Atlassian.JIRA.
Jira (PUP-9958) Cannot add custom CA certs for internal resources without replacing bundled CA
Title: Message Title Josh Cooper moved an issue Puppet / PUP-9958 Cannot add custom CA certs for internal resources without replacing bundled CA Change By: Josh Cooper Affects Version/s: puppet-agent 5.3.5 Key: PA PUP - 2335 9958 Project: Puppet Agent Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.286210.1542994571000.52214.1565641560422%40Atlassian.JIRA.
Jira (PUP-9957) puppet apply command fails when external modules are installed
Title: Message Title Josh Cooper commented on PUP-9957 Re: puppet apply command fails when external modules are installed This may be related to additional checking introduced in 5.5.x to ensure modules don't declare things outside of their module namespace, eg PUP-4242 or PUP-9020. /cc Kris Bosland, Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.313933.1561476226000.52198.1565641260262%40Atlassian.JIRA.
Jira (PUP-9957) puppet apply command fails when external modules are installed
Title: Message Title Josh Cooper moved an issue Puppet / PUP-9957 puppet apply command fails when external modules are installed Change By: Josh Cooper Affects Version/s: puppet-agent 5.5.10 Key: PA PUP - 2753 9957 Project: Puppet Agent Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.313933.1561476226000.52179.1565640960574%40Atlassian.JIRA.
Jira (PUP-9316) implement no_proxy in puppet.conf
Title: Message Title Josh Cooper commented on PUP-9316 Re: implement no_proxy in puppet.conf Merged in https://github.com/puppetlabs/puppet/commit/fcdf8692a0d83ba6d5eec96e18a19b9aa7c3517e Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.285347.1542320475000.52163.1565639881022%40Atlassian.JIRA.
Jira (BOLT-1384) Inventory command
Title: Message Title Lucy Wyman commented on BOLT-1384 Re: Inventory command Corey Osman What's your use case? I don't follow why –format json doesn't work. You could theoretically use tee to send the output to another stream / file, if you want to both read it and consume it. Is the human formatting what you need for it to be consumed? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.312167.1560296026000.52063.1565635800346%40Atlassian.JIRA.
Jira (PDB-3922) Build from source instructions don't work outside our network
Title: Message Title Sara Meisburger updated an issue PuppetDB / PDB-3922 Build from source instructions don't work outside our network Change By: Sara Meisburger Sprint: Release Engineering Grooming Hopper Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.249492.1525718874000.51941.1565631900621%40Atlassian.JIRA.
Jira (PDB-3922) Build from source instructions don't work outside our network
Title: Message Title Sara Meisburger assigned an issue to Morgan Rhodes PuppetDB / PDB-3922 Build from source instructions don't work outside our network Change By: Sara Meisburger Assignee: Morgan Rhodes Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.249492.1525718874000.51946.1565631900653%40Atlassian.JIRA.
Jira (PUP-9585) Do not output password for user type if it is marked Sensitive
Title: Message Title Josh Cooper commented on PUP-9585 Re: Do not output password for user type if it is marked Sensitive Passed CI in 8df45b80bb Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.302109.1553793067000.51885.1565631301044%40Atlassian.JIRA.
Jira (PUP-9585) Do not output password for user type if it is marked Sensitive
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9585 Do not output password for user type if it is marked Sensitive Change By: Josh Cooper Fix Version/s: PUP 6.8.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.302109.1553793067000.51893.1565631301109%40Atlassian.JIRA.
Jira (PUP-9942) no_proxy environment variable does not work
Title: Message Title Josh Cooper commented on PUP-9942 Re: no_proxy environment variable does not work Passed CI in 8df45b80bb Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.320046.1565215526000.51881.1565631240198%40Atlassian.JIRA.
Jira (PDB-1880) org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "reports_pkey"
Title: Message Title James Glenn assigned an issue to James Glenn I have not been able to reproduce since upgrading versions. PuppetDB / PDB-1880 org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "reports_pkey" Change By: James Glenn Resolution: Cannot Reproduce Assignee: James Glenn Status: Open Closed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9943) User type has custom retrieve() with non-standard return values
Title: Message Title Jorie Tappa updated an issue Puppet / PUP-9943 User type has custom retrieve() with non-standard return values Change By: Jorie Tappa Team: Coremunity Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.320115.1565272699000.51752.1565629020790%40Atlassian.JIRA.
Jira (PUP-9956) Exec logs output of Sensitive unless and onlyif checks at debug
Title: Message Title Jorie Tappa assigned an issue to Kris Bosland Puppet / PUP-9956 Exec logs output of Sensitive unless and onlyif checks at debug Change By: Jorie Tappa Assignee: Kris Bosland Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.320444.1565385879000.51736.1565628960197%40Atlassian.JIRA.
Jira (PUP-9730) Connections with multiple addresses for a host should try ALL addresses for that host
Title: Message Title Jorie Tappa assigned an issue to Kris Bosland Puppet / PUP-9730 Connections with multiple addresses for a host should try ALL addresses for that host Change By: Jorie Tappa Assignee: Kris Bosland Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.311671.1559920061000.51708.1565627940218%40Atlassian.JIRA.
Jira (PDB-4478) posgresql crashed with glibc detected DELETE: double free or corruption (!prev) PE 2018.1.4.1 on PostgreSQL 9.6.10
Title: Message Title Gareth McGrillan commented on PDB-4478 Re: posgresql crashed with glibc detected DELETE: double free or corruption (!prev) PE 2018.1.4.1 on PostgreSQL 9.6.10 The Puppet DB team found the following PG issue which is similar : https://www.postgresql.org/message-id/flat/152296798225.31227.6026116154621550125%40wrigleys.postgresql.org I don't see anything specifically resolved in the PG 9.6.10 release notes on this case so am not entirely sure if it was resolved. I am checking with the customer that they are not using an external monitoring source (like Zappix in the above ticket)... Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.320500.156561791.51449.1565618160233%40Atlassian.JIRA.
Jira (PDB-4478) posgresql crashed with glibc detected DELETE: double free or corruption (!prev) PE 2018.1.4.1 on PostgreSQL 9.6.10
Title: Message Title Gareth McGrillan created an issue PuppetDB / PDB-4478 posgresql crashed with glibc detected DELETE: double free or corruption (!prev) PE 2018.1.4.1 on PostgreSQL 9.6.10 Issue Type: Bug Assignee: Unassigned Attachments: pe-amer2pg1_crash.txt Components: PuppetDB Created: 2019/08/12 6:51 AM Priority: Normal Reporter: Gareth McGrillan From zendesk: https://puppetlabs.zendesk.com/agent/tickets/35750 Postgresql crashed but recovered with the titled error. The customer was looking to know the reason for the crash and if it could be avoided. Also, if there was any data that might need to be rectified. Some highlights from the logs pe-amer2pg1_crash.txt Add Comment
Jira (PUP-5109) Puppet::Resource::Catalog::Compiler#set_server_facts always produces a warning on ipv6 only systems
Title: Message Title Igor Galić commented on PUP-5109 Re: Puppet::Resource::Catalog::Compiler#set_server_facts always produces a warning on ipv6 only systems I essentially agree with the things in this comment https://github.com/puppetlabs/puppet/pull/7656#issuecomment-519183617 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.95553.144084808.51410.1565609700180%40Atlassian.JIRA.
Jira (FACT-1983) Detect OS
Title: Message Title Sebastian Miclea assigned an issue to Sebastian Miclea Facter / FACT-1983 Detect OS Change By: Sebastian Miclea Assignee: Sebastian Miclea Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.319545.1564991823000.51316.1565595480351%40Atlassian.JIRA.
