Jira (PUP-9008) puppet-agent-5.5.4-1.el6.x86_64 on Scientfic Linux 6 fails to use upstart
Title: Message Title Michelle Fredette updated an issue Puppet / PUP-9008 puppet-agent-5.5.4-1.el6.x86_64 on Scientfic Linux 6 fails to use upstart Change By: Michelle Fredette Labels: docs_reviewed linux redhat regression service upstart 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9010) Puppetserver fails to compile catalog when disable_i18n = true
Title: Message Title Michelle Fredette updated an issue Puppet / PUP-9010 Puppetserver fails to compile catalog when disable_i18n = true Change By: Michelle Fredette Labels: docs_reviewed 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9024) tagged function should downcase arguments
Title: Message Title Michelle Fredette updated an issue Puppet / PUP-9024 tagged function should downcase arguments Change By: Michelle Fredette Labels: docs_reviewed 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9027) Deprecate CA-related settings in puppet.conf
Title: Message Title Michelle Fredette updated an issue Puppet / PUP-9027 Deprecate CA-related settings in puppet.conf Change By: Michelle Fredette Labels: docs_reviewed 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-685) Race condition in transport logger initialization
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-685 Race condition in transport logger initialization Change By: Michael Smith Assignee: Michael Smith 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8581) Extract zone type/provider into a module
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8581 Extract zone type/provider into a module Change By: Josh Cooper Release Notes Summary: bundled + supported: The zone type and provider has been extracted into a module (https://forge.puppet.com/puppetlabs/zone_core) and is vendored into 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8568) Extract cron type/provider into a module
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8568 Extract cron type/provider into a module Change By: Josh Cooper Release Notes Summary: supported + bundled: The cron type and provider has been extracted into a module (https://forge.puppet.com/puppetlabs/cron_core) and is vendored into puppet-agent Release Notes: New Feature 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1077) Extract nagios type/provider into a module
Title: Message Title Josh Cooper updated an issue Puppet / PUP-1077 Extract nagios type/provider into a module Change By: Josh Cooper Release Notes Summary: deprecated: The Nagios types no longer ship with Puppet, and are now available as the puppetlabs/nagios_core module from the Forge. 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8567) Extract augeas type/provider into a module
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8567 Extract augeas type/provider into a module Change By: Josh Cooper Release Notes Summary: supported + bundled: The augeas feature, type and provider has been moved to the a module: https://forge.puppet.com/puppetlabs/augeas_core. It is also repackaged in 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8579) Extract yumrepo type/provider into a module
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8579 Extract yumrepo type/provider into a module Change By: Josh Cooper Release Notes Summary: supported + bundled: The yumrepo type and provider has been moved to the a module: https://forge.puppet.com/puppetlabs/yumrepo_core. It is also repackaged in 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8578) Extract sshkeys type/provider into a module
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8578 Extract sshkeys type/provider into a module Change By: Josh Cooper Release Notes Summary: supported + bundled: The sshkey and ssh_authorized_keys types have been moved into the sshkeys_core module on the Forge. This module is being repackaged into puppet-agent so that it is available 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8572) Extract maillist type/provider into a module
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8572 Extract maillist type/provider into a module Change By: Josh Cooper Release Notes Summary: unbundled but active: Maillist has been extracted from the main puppet codebase. The module now lives in a seperate codebase and is available on the forge as puppetlabs/maillist_core. The module is now bundled as a component of the puppet-agent package, so the user should not notice any changes. 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8571) Extract mailalias type/provider into a module
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8571 Extract mailalias type/provider into a module Change By: Josh Cooper Release Notes Summary: unbundled but active: Mailalias has been extracted from the main puppet codebase. The module now lives in a seperate codebase and is available on the forge as puppetlabs/mailalias_core. The module is now bundled as a component of the puppet-agent package, so the user should not notice any changes. 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8569) Extract host type/provider into a module
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8569 Extract host type/provider into a module Change By: Josh Cooper Release Notes Summary: supported + bundled: The host type and provider has been moved to a module: https://forge.puppet.com/puppetlabs/host_core. It is also repackaged in 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8580) Extract zfs type/provider into a module
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8580 Extract zfs type/provider into a module Change By: Josh Cooper Release Notes Summary: supported + bundled: ZFS/ZPool have been extracted from the main puppet codebase. The module now lives in a seperate codebase and is available on the forge as puppetlabs/zfs_core. The module is now bundled as a component of the puppet-agent package, so the user should not notice any changes. 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8577) Extract selinux type/provider into a module
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8577 Extract selinux type/provider into a module Change By: Josh Cooper Release Notes Summary: supported + bundled: The selboolean and selmodule types and providers have been moved to a module: https://forge.puppet.com/puppetlabs/selinux_core, and it is repackaged into puppet-agent 6.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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8575) Extract network_device type/provider into a module
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8575 Extract network_device type/provider into a module Change By: Josh Cooper Release Notes Summary: deprecated: The cisco network device types no longer ship with Puppet. These types and providers have been deprecated in favor of the puppetlabs/cisco_ios module which is available on the forge. 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8574) Extract mount type/provider into a module
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8574 Extract mount type/provider into a module Change By: Josh Cooper Release Notes Summary: supported + bundled: The mount type and provider has been moved to a module: https://forge.puppet.com/puppetlabs/mount_core. It is also repackaged in 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8570) Extract k5login type/provider into a module
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8570 Extract k5login type/provider into a module Change By: Josh Cooper Release Notes Summary: unbundled but active: The k5login type and provider has been moved to a module: https://forge.puppet.com/puppetlabs/k5login_core. It is NOT repackaged in 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8573) Extract macdslocal type/provider into a module
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8573 Extract macdslocal type/provider into a module Change By: Josh Cooper Release Notes Summary: deprecated: The computer, macauthorization, and mcx types and providers have been moved to a module: https://forge.puppet.com/puppetlabs/macdslocal_core. It is not being repackaged into puppet-agent for 6.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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8576) Extract scheduled_task type/provider into a module
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8576 Extract scheduled_task type/provider into a module Change By: Josh Cooper Release Notes Summary: supported + bundled: The scheduled_task type and provider has been extracted into a module (https://forge.puppet.com/puppetlabs/scheduled_task) and is vendored into 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5985) Features are not being re-evaluated when a block is used
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5985 Features are not being re-evaluated when a block is used Change By: Josh Cooper Release Notes Summary: Features now behave consistently when passed defined using a block or a list of libraries now behave the same, so the following are equivalent :Puppet.features.add(:my_feature) do # some code require 'mylib' end or an explicit list of ruby libraries: Puppet.features.add(:my_feature, libs: ['my_lib']) By default, puppet's feature subsystem does not cache misses, as Previously the result of the block was always cached. With this change only true or false return values are cached. To indicate that the state of the feature is unknown and may become true while applying a catalog. However available later , if always_retry_plugins is false, then both the block and non-block forms will cache misses, which is important for puppetserver should return nil . 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 po
Jira (PUP-9027) Deprecate CA-related settings in puppet.conf
Title: Message Title Michelle Fredette commented on PUP-9027 Re: Deprecate CA-related settings in puppet.conf thank you! 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1870) Stdout in facts invalidates formatted output (yaml/json)
Title: Message Title
Eric Sorenson commented on FACT-1870
Re: Stdout in facts invalidates formatted output (yaml/json)
FWIW I confirmed that using the Facter.error helper method in the rescue block provides clean STDOUT/STDERR separation - So with the fact below, facter -p -j | jq . works even with the error-generating output. The fact that these helper methods and best practice is folklore is a problem, which recent doc updates will help address, but it needs more developer-centric attention.
Facter.add('test') do
confine :kernel => 'Linux'
begin
test = 'nomatch'
test = Facter.value(:doesntexist).strip()
setcode { test }
rescue Exception => ex
Facter.error "#{File.basename(__FILE__)} - ruby fact threw an exception: #{ex}"
end
end
eric@cloudline> facter -j --custom-dir ~/.puppetlabs/etc/facter/lib >
Jira (FACT-1653) External Facts from PowerShell do not parse structured output (JSON/YAML)
Title: Message Title Reid Vandewiele commented on FACT-1653 Re: External Facts from PowerShell do not parse structured output (JSON/YAML) Note on syntax, single-quotes are not valid JSON. Kevin Reeuwijk is that a typo? 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1653) External Facts from PowerShell do not parse structured output (JSON/YAML)
Title: Message Title
Kevin Reeuwijk commented on FACT-1653
Re: External Facts from PowerShell do not parse structured output (JSON/YAML)
Larissa Lane you may want to include this in the GSWP training:
Basic facts: write a script that generates:
fact_name = fact_value
Structured facts: write a script that generates:
{'fact_name': }
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (FACT-1653) External Facts from PowerShell do not parse structured output (JSON/YAML)
Title: Message Title
Kevin Reeuwijk commented on FACT-1653
Re: External Facts from PowerShell do not parse structured output (JSON/YAML)
Validated, this works:
$result = $PSVersionTable | ConvertTo-Json -Compress
Write-Host "{'a_test_fact':$result}"
It indeed fails if the fact name isn't quoted (single quotes do work fortunately). One way to validate if the user is generating valid JSON is to do this:
$result = $PSVersionTable | ConvertTo-Json -Compress
$test = "{'a_test_fact':$result}"
$test | ConvertFrom-Json
If the data isn't properly formatted (e.g. using = instead of a colon) then the ConvertFrom-Json command will fail. The only thing ConvertFrom-Json doesn't catch is if the fact name isn't quoted, as Windows automatically quotes this during the conversion. Thanks Branan Riley for the guidance!
Add Comment
Jira (FACT-1653) External Facts from PowerShell do not parse structured output (JSON/YAML)
Title: Message Title Kevin Reeuwijk commented on FACT-1653 Re: External Facts from PowerShell do not parse structured output (JSON/YAML) OK, trying it with the output changes as suggested 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1653) External Facts from PowerShell do not parse structured output (JSON/YAML)
Title: Message Title Branan Riley commented on FACT-1653 Re: External Facts from PowerShell do not parse structured output (JSON/YAML) I've filed FACT-1876 for us to improve the documentation regarding structured output from executable facts 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1876) Provide better documentation on structured executable facts
Title: Message Title Branan Riley created an issue Facter / FACT-1876 Provide better documentation on structured executable facts Issue Type: Improvement Assignee: Unassigned Created: 2018/08/17 12:26 PM Priority: Normal Reporter: Branan Riley The documentation for external structured facts describes a top-level hash object containing keys that indicate facts to merge into the result. The docs for executable facts don't reference this to explain how they behave when JSON/YAML output is desired. This should be improved so that it's clearer that one cannot use the key=value output format to create structured data in Facter. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca9
Jira (FACT-1653) External Facts from PowerShell do not parse structured output (JSON/YAML)
Title: Message Title
Branan Riley commented on FACT-1653
Re: External Facts from PowerShell do not parse structured output (JSON/YAML)
JSON/YAML output from powershell is parsed the same as if it were a static json or yaml file - it should be a single hash at the top level, with keys indicating the facts to process. Thus, the output for your desired behavior should be
{a_test_fact:}
We do this specifically for the issue you noticed when you do not compress the output - it's not easy to tell if multiple lines are "more data for a structured fact" or "another key/value pair for a new fact". Running facter with `--debug` in both cases should give you more information about how Facter is trying to parse your output.
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 post to this group, send email to puppet-bugs@googleg
Jira (BOLT-772) Handle poorly-behaved providers
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-772 Handle poorly-behaved providers Change By: Michael Smith Release Notes Summary: On Windows, providers that keep file handles open failing to remove the temporary modulepath will no longer prevent the apply from finishing successfully. It will however leave the directory around on the target. 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-772) Handle poorly-behaved providers
Title: Message Title Michael Smith commented on BOLT-772 Re: Handle poorly-behaved providers This might not actually be providers, it may just be the first time we used custom providers on Windows. 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-772) Handle poorly-behaved providers
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-772 Handle poorly-behaved providers Change By: Michael Smith Release Notes Summary: Providers On Windows, providers that keep file handles open will no longer prevent the apply from crashing finishing successfully . It will however leave the directory around on the target. 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-772) Handle poorly-behaved providers
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-772 Handle poorly-behaved providers Change By: Alex Dreyer Release Notes Summary: Providers that keep file handles open will no longer prevent the apply from crashing. It will however leave the directory around on the target. Release Notes: Bug Fix 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-772) Handle poorly-behaved providers
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-772 Handle poorly-behaved providers Change By: Alex Dreyer Fix Version/s: BOLT Next 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-789) Ship with Ruby 2.5
Title: Message Title Michael Smith created an issue Puppet Task Runner / BOLT-789 Ship with Ruby 2.5 Issue Type: Improvement Assignee: Unassigned Created: 2018/08/17 10:54 AM Priority: Normal Reporter: Michael Smith Puppet 6 has decided they're going to ship with Ruby 2.5, and done all the prep work for us. We should bump Bolt to use Ruby 2.5 for any performance boosts this might give. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-4013) Find bash via /usr/bin/env in ext/cli/foreground, etc.
Title: Message Title Rob Browning created an issue PuppetDB / PDB-4013 Find bash via /usr/bin/env in ext/cli/foreground, etc. Issue Type: Improvement Assignee: Unassigned Created: 2018/08/17 10:33 AM Fix Versions: PDB 6.0.0 Priority: Normal Reporter: Rob Browning 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
Jira (PUP-6919) Puppet::Util::Windows::Process.execute should accept a working directory
Title: Message Title Enis Inan updated an issue Puppet / PUP-6919 Puppet::Util::Windows::Process.execute should accept a working directory Change By: Enis Inan Sprint: Platform OS 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6919) Puppet::Util::Windows::Process.execute should accept a working directory
Title: Message Title Enis Inan assigned an issue to Enis Inan Puppet / PUP-6919 Puppet::Util::Windows::Process.execute should accept a working directory Change By: Enis Inan Assignee: Enis Inan 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1653) External Facts from PowerShell do not parse structured output (JSON/YAML)
Title: Message Title Kevin Reeuwijk updated an issue Facter / FACT-1653 External Facts from PowerShell do not parse structured output (JSON/YAML) Change By: Kevin Reeuwijk Attachment: Screen Shot 2018-08-17 at 7.19.18 PM.png 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-788) Modify bolt to accept new expect API structure (without options)
Title: Message Title Lucy Wyman commented on BOLT-788 Re: Modify bolt to accept new expect API structure (without options) We've made changes to the API in: https://docs.google.com/document/d/1iZKHlb0z7jMk0ER3tSJ4Mm2kGmvZp7HdaaJTd9rXp8g/edit# but those changes aren't reflected in bolt yet. So the API it expects is different from the one we've defined. For example, bolt looks for an 'options' hash under target, but there isn't one. 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1653) External Facts from PowerShell do not parse structured output (JSON/YAML)
Title: Message Title Kevin Reeuwijk commented on FACT-1653 Re: External Facts from PowerShell do not parse structured output (JSON/YAML) This issue is not resolved in the latest version of facter (3.11.3 at time of this writing). Take this example external fact: $result = $PSVersionTable | ConvertTo-Json -Compress Write-Host "a_test_fact=$result" This should result in a structured fact in PE. However the actual fact in PE looks like the attached screenshot. It is clearly not getting detected as JSON data, and thus not getting parsed as such. If the -Compress option is not provided to Powershell, only the first line of JSON data ends up in PE. 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 a
Jira (BOLT-788) Modify bolt to accept new expect API structure (without options)
Title: Message Title Lucy Wyman commented on BOLT-788 Re: Modify bolt to accept new expect API structure (without options) Honestly it's made using pe-bolt-server at the moment such a pain I'm tempted to attach the changes to 722, but I don't want to overload PRs. 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7312) Confine systemd provider to init system matching systemd
Title: Message Title Geoff Nichols assigned an issue to Branan Riley Puppet / PUP-7312 Confine systemd provider to init system matching systemd Change By: Geoff Nichols Assignee: Branan Riley 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-788) Modify bolt to accept new expect API structure (without options)
Title: Message Title Michael Smith commented on BOLT-788 Re: Modify bolt to accept new expect API structure (without options) I don't understand this 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-707) Docs for how to use 'apply' in a plan
Title: Message Title Michael Smith assigned an issue to Kate Lopresti Puppet Task Runner / BOLT-707 Docs for how to use 'apply' in a plan Change By: Michael Smith Assignee: Kate Lopresti 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1653) External Facts from PowerShell do not parse structured output (JSON/YAML)
Title: Message Title Larissa Lane commented on FACT-1653 Re: External Facts from PowerShell do not parse structured output (JSON/YAML) Branan Riley Kevin mentioned in training this morning that this issue doesn't appear to be resolved. 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9072) Use repeated_param UX for Deferred()
Title: Message Title Reid Vandewiele commented on PUP-9072 Re: Use repeated_param UX for Deferred() HipChat Sensitive Data room, Friday August 17, 2018 [7:41 AM] Henrik Lindberg: @turbodog @TonyVu There was a question in the demo about the use of an array for the arguments. This was kind of a design choice. [7:42 AM] Henrik Lindberg: It has to do with calling "new" on a type, and creating a serializeable object. That simply maps each given value to an attribute, and arguments is an array, so it must be one in the call. [7:44 AM] Henrik Lindberg: That can probably be changed if we so desire. What it prevents though is to give Deferred additional arguments in the future. That could for instance be a return type check, or something that prevents a Deferred from being automatically resolved (i.e. you want it to be sent all the way to a resource provider and that the provider resolves the value (i.e. makes the call). [7:46 AM] Henrik Lindberg: For those reasons I thought we could just as well keep the arguments as an array. [7:52 AM] Lindsey Smith: @ReidVandewiele ^^^ [8:43 AM] Reid Vandewiele: I filed PUP-9072 with my thoughts on the UX. I understand how an explicit array is technically more powerful in that it "leaves the door open" to potential future extensions. It's not free though; requiring an Array argument costs UX consistency and simplicity. [8:43 AM] Reid Vandewiele: Barring a known future use case we believe would be adopted >20% of the time, I would make the UX choice to close that door in favor of simplifying how the majority of our customers will write and use Deferred. [8:44 AM] Reid Vandewiele: ...Especially if we have the option of using a different signature, e.g. Deferred( Hash ), to account for yet-unknown complex use cases in the future. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8320) True/truthy inconsistencies between function filter() and functions all() and any()
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-8320
True/truthy inconsistencies between function filter() and functions all() and any()
Change By:
Henrik Lindberg
Release Notes Summary:
The {{filter}} function did not accept truthy value returned from the block as indication of values to include in the result. Only exactly boolean {{true}} was earlier accepted.
Release Notes:
Bug Fix
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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-743) Document bolt-server API endpoints
Title: Message Title Cas Donoghue assigned an issue to Cas Donoghue Puppet Task Runner / BOLT-743 Document bolt-server API endpoints Change By: Cas Donoghue Assignee: Cas Donoghue 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9074) Windows scheduled_task name cannot us a path
Title: Message Title
Peter J Krawetzky created an issue
Puppet / PUP-9074
Windows scheduled_task name cannot us a path
Issue Type:
Bug
Affects Versions:
PUP 4.10.4
Assignee:
Unassigned
Components:
Windows
Created:
2018/08/17 7:09 AM
Priority:
Normal
Reporter:
Peter J Krawetzky
Puppet Version: 4.10.4 Puppet Server Version: 5.3.4 OS Name/Version: Windows 2016 10.0.14393 When trying to execute the follow resource on a Windows 2016 server an error is returned: scheduled_task { '\Puppet\PuppetKickoff': ensure => present, enabled => true, command => 'powershell.exe', arguments => ' E:Program Files\\PuppetLabs\\binrun_puppet_shell.bat -Verb runas', trigger => { schedule => daily, every => 1, # Specifies every other day. Defaults to 1 (every day). start_time => '08:${puppet_agent::params::cronminute}', # Must be specified minutes_interval => '60', # Repeat this task every 60 minutes minutes_duration => '300', # The task will run for a total of five hours } Error: Error: Failed to call #::NewWorkItem with HRESULT: -2147024893.: The system cannot find the path specified. Error: /Stage[main]/Puppet_agent::Init_windows/Scheduled_task[\Puppet\PuppetKickoff]/ensure: change from absent to present failed: Failed to call #::NewWorkItem with HRESULT: -2147024893.: The system cannot find the path specified. When I only use PuppetKickoff in the name, it sucessfully creates a scheduled task but not in the path I desire. Desired Behavior: Allow a path structure in the scheduled_task name in order to place a task away from the main path Actual Behavior: See above
Jira (FACT-1875) Unable to use "confine" with structured facts -- documentation is incorrect
Title: Message Title Chris Butler commented on FACT-1875 Re: Unable to use "confine" with structured facts -- documentation is incorrect For anyone paying attention, I realised my error with the "code block" style confine check as soon as I pressed submit (typical!). However it still seems like the Facter.value method mentioned in the docs doesn't work, unless I'm also missing something there! 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1875) Unable to use "confine" with structured facts -- documentation is incorrect
Title: Message Title
Chris Butler updated an issue
Facter / FACT-1875
Unable to use "confine" with structured facts -- documentation is incorrect
Change By:
Chris Butler
I've been attempting to {{confine}} some facts using structured facts, as described in [the documentation here|https://puppet.com/docs/facter/3.11/custom_facts.html#confining-facts]. However, neither the first method described in the docs seems documentation using Facter.value does not seem to actually work with the current version of facter :{code} ==> oscheck_codeblock.rb <== Facter.add(:oscheck_codeblock) do confine :os do |os| os['id'] == 'Debian' end setcode do 'fact value' endend== > oscheck_factervalue.rb <==Facter.add(:oscheck_factervalue) do confine Facter.value(:os)[' distro'][' id'] => 'Debian' setcode do 'fact value' endend{code}Running facter with FACTERLIB pointed at the location of the above two files file gives:{code}2018-08-17 13: 21 28 : 09 22 . 126211 140537 INFO puppetlabs.facter - executed with command line: --debug oscheck_codeblock oscheck_factervalue.2018-08-17 13: 21 28 : 09 22 . 126619 140979 DEBUG leatherman.ruby:504 - ruby was found at "/usr/bin/ruby".2018-08-17 13: 21 28 : 09 22 . 126762 141139 DEBUG leatherman.execution:93 - executing command: /usr/bin/ruby -e print(['libdir', 'archlibdir', 'sitearchlibdir', 'bindir'].find do |name|dir = RbConfig::CONFIG[name];next unless dir;file = File.join(dir, RbConfig::CONFIG['LIBRUBY_SO']);break file if File.exist? file;false end)2018-08-17 13: 21 28 : 09 22 . 242077 295315 DEBUG | - /usr/lib/x86_64-linux-gnu/libruby-2.3.so.2.3.02018-08-17 13: 21 28 : 09 22 . 242280 295528 DEBUG leatherman.execution:559 - process exited with status code 0.2018-08-17 13: 21 28 : 09 22 . 246717 299951 INFO leatherman.ruby:137 - ruby loaded from "/usr/lib/x86_64-linux-gnu/libruby-2.3.so.2.3.0".2018-08-17 13: 21 28 : 09 22 . 247314 300503 DEBUG leatherman.dynamic_library:77 - symbol rb_data_object_alloc not found in library /usr/lib/x86_64-linux-gnu/libruby-2.3.so.2.3.0, trying alias rb_data_object_wrap.2018-08-17 13: 21 28 : 09 22 . 357056 418246 INFO leatherman.ruby:186 - using ruby version 2.3.32018-08-17 13: 21 28 : 09 22 . 357220 418408 INFO puppetlabs.facter - requested queries: oscheck_codeblock oscheck_factervalue.2018-08-17 13: 21 28 : 09 22 . 357303 418488 DEBUG puppetlabs.facter - fact "facterversion" has resolved to "3.11.3".2018-08-17 13: 21 28 : 09 22 . 357678 418857 DEBUG leatherman.file_util:65 - Error reading file: No such file or directory2018-08-17 13: 21 28 : 09 22 . 358390 419635 DEBUG puppetlabs.facter - loading all custom facts.2018-08-17 13: 21 28 : 09 22 . 358435 419683 DEBUG puppetlabs.facter - loading custom fact directories from config file2018-08-17 13: 21 28 : 09 22 . 358494 419733 DEBUG puppetlabs.facter - searching for custom facts in /home/chrisb.2018-08-17 13: 21 28 : 09 22 . 358649 419890 INFO puppetlabs.facter - loading custom facts from /home/chrisb/ oscheck_codeblock.rb.2018-08-17 13:21:09.358964 IN
Jira (FACT-1875) Unable to use "confine" with structured facts -- documentation is incorrect
Title: Message Title Chris Butler updated an issue Facter / FACT-1875 Unable to use "confine" with structured facts -- documentation is incorrect Change By: Chris Butler Summary: Unable to use "confine" with structured facts -- documentation error is incorrect 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1875) Unable to use "confine" with structured facts -- documentation error
Title: Message Title Chris Butler created an issue Facter / FACT-1875 Unable to use "confine" with structured facts -- documentation error Issue Type: Bug Affects Versions: FACT 3.11.3 Assignee: Unassigned Created: 2018/08/17 5:25 AM Environment: Tested with Facter 3.6.7 running on VirtuozzoLinux 7 Also tested with Facter 3.11.3 on Debian Stretch Priority: Normal Reporter: Chris Butler I've been attempting to confine some facts using structured facts, as described in the documentation here. However, neither method described in the docs seems to actually work with the current version of facter: ==> oscheck_codeblock.rb <== Facter.add(:oscheck_codeblock) do confine :os do |os| os['id'] == 'Debian'
Jira (PUP-9040) puppet lookup command returns warning with poor formatting
Title: Message Title Henrik Lindberg commented on PUP-9040 Re: puppet lookup command returns warning with poor formatting Thanks Paul Schaffer, can you try to do a puppet apply with a lookup function call and see if that triggers an error. 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
