Jira (PDOC-90) Strings should be able to document a single, specific module
Title: Message Title William Hopper created an issue Puppet Strings / PDOC-90 Strings should be able to document a single, specific module Issue Type: Bug Assignee: Unassigned Created: 2016/09/12 4:43 PM Priority: Normal Reporter: William Hopper Right now, strings will either parse a specific named file or everything in the current directory. There should be a puppet strings module command of some sort to document a specific module Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PDOC-88) Create a plan for ensuring strings support going forward
Title: Message Title William Hopper commented on PDOC-88 Re: Create a plan for ensuring strings support going forward Todo: investigate what we have setup for strings in CI right now. We'd like to run the latest version of strings against a small fixture suite (acceptance). A 'don't break strings' acceptance test in puppet may be the way to do this. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (PDOC-83) Define a proper JSON schema for strings
Title: Message Title William Hopper commented on PDOC-83 Re: Define a proper JSON schema for strings Todo: confirm Peter's schema works for docs. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (PDOC-82) Ensure the strings gem can be managed via bundler in docs scripts
Title: Message Title William Hopper commented on PDOC-82 Re: Ensure the strings gem can be managed via bundler in docs scripts Todo: make sure runtime dependencies are managed in the gemspec rather than the Gemfile. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (PDOC-82) Ensure the strings gem can be managed via bundler in docs scripts
Title: Message Title William Hopper assigned an issue to Peter Huene Puppet Strings / PDOC-82 Ensure the strings gem can be managed via bundler in docs scripts Change By: William Hopper Assignee: Peter Huene Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (PDOC-61) Strings finds bogus "function_definition" function
Title: Message Title William Hopper assigned an issue to Peter Huene Puppet Strings / PDOC-61 Strings finds bogus "function_definition" function Change By: William Hopper Assignee: Peter Huene Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (PDOC-60) Strings skips docs for the log message functions
Title: Message Title William Hopper commented on PDOC-60 Re: Strings skips docs for the log message functions Todo: figure out priority on this. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (PDOC-63) Strings outputs errors on puppet core
Title: Message Title William Hopper commented on PDOC-63 Re: Strings outputs errors on puppet core Note on this: Peter's work fixes this on the strings side, but we'll still need to go into core and make a lot of docs updates. Peter also mentioned we should limit what strings looks at in core. Right now it globs all of lib/, but really we just want functions, types, providers, etc. Once Peter's work is merged in, we can effectively call this ticket done. The work to update core docs is tracked in PDOC-87. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-5831) Add a Binary type and runtime object
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5831 Add a Binary type and runtime object Change By: Henrik Lindberg Acceptance Criteria: This is the first step in adding a Binary Type. The criteria for this step are:* It should be possible to create a Binary from:** a base64 encoded strings in strict, relaxed, and URL safe base64 encoding** a file (any content)** an Array of integer byte values, including an empty array* It should be possible to acces one or more of the bytes using [n] or [n, n] syntax (as with a String) to produce a new Binary with the sub-sequence* It should be possible to convert a Binary** to String using different formats (base64 strict, relaxed, URL safe), as opaque redacted 'binary' or "Binary" string value, or as an Array of Integers** to Array of Integers* It should be possible to use a Binary value as contents of a File resource Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (PDOC-84) Add the ability to generate only JSON
Title: Message Title William Hopper assigned an issue to Peter Huene Puppet Strings / PDOC-84 Add the ability to generate only JSON Change By: William Hopper Assignee: Peter Huene Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (PDOC-87) Ensure our internal functions, types, and providers are documented in a way that's compatible with strings
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-87 Ensure our internal functions, types, and providers are documented in a way that's compatible with strings Change By: William Hopper Summary: Ensure our internal functions , types, and providers are documented in a way that's compatible with strings Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (PDOC-63) Strings outputs errors on puppet core
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-63 Strings outputs errors on puppet core Change By: William Hopper Summary: Blizzard of Strings outputs errors and warnings when run against on puppet core code Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (PDOC-87) Ensure our internal functions are documented in a way that's compatible with strings
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-87 Ensure our internal functions are documented in a way that's compatible with strings Change By: William Hopper Story Points: 1 3 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (PDOC-85) Handle the case of 4x functions and 3x stubs
Title: Message Title William Hopper commented on PDOC-85 Re: Handle the case of 4x functions and 3x stubs Todo: talk to docs Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-5831) Add a Binary type and runtime object
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5831 Add a Binary type and runtime object Change By: Henrik Lindberg Sprint: PDS Triage 2016-09-21 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6687) lest and then functions not well referenced in the documentation
Title: Message Title Nicholas Fagerlund commented on PUP-6687 Re: lest and then functions not well referenced in the documentation The doc stubs in lib/puppet/parser/functions are causing a conflict. Since they were created with a copy-paste error, the system thinks there are two 3.x "lest" functions, and the later one (actually "then") is winning. One-word fix, but I need to figure out which branch to PR against. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6641) Integration test for Windows service fails on Windows 10
Title: Message Title
Moses Mendoza commented on PUP-6641
Re: Integration test for Windows service fails on Windows 10
Validated that impacted tests pass on a clean install of Windows 10
C:\Users\moses\development\puppet [master ≡]> bundle exec rspec --format documentation --color .\spec\integration\provider\service\windows_spec.rb
DL is deprecated, please use Fiddle
Run options: exclude {:broken=>true, :benchmark=>true}
Puppet::Type::Service::ProviderWindows (integration)
should fail querying services that do not exist
with a Puppet::Error when querying enabled?
with a Puppet::Error when querying status
should return valid values when querying a service that does exist
with a valid enabled? value when asked if enabled
Jira (PDOC-55) @!puppet.type.parameter (and property) directive should be able to add metadata
Title: Message Title Nicholas Fagerlund commented on PDOC-55 Re: @!puppet.type.parameter (and property) directive should be able to add metadata This doesn't appear to have any info about what this is for, so in short: Ruby-based types and providers can use all kinds of impenetrable metaprogramming to tersely create objects, and it seems impossible to determine what those objects are (and what their docstrings are) with a YARD-like static analysis of the code. To document things like the core Nagios types, we need an ability to explicitly override metadata for objects in a resource type. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (PDB-3049) (maint) Update PDB to use new signing key
Title: Message Title gepetto-bot updated an issue PuppetDB / PDB-3049 (maint) Update PDB to use new signing key Change By: gepetto-bot Sprint: EP 2016-09-21 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (PDB-3049) (maint) Update PDB to use new signing key
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3049 (maint) Update PDB to use new signing key Issue Type: Bug Assignee: Unassigned Created: 2016/09/12 2:13 PM Priority: Normal Reporter: gepetto-bot We are in the process of introducing a new signing key. This commit updates PDB to switch from the old key to the new one Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6457) Mount resources could handle invalid options better
Title: Message Title Branan Riley updated an issue Puppet / PUP-6457 Mount resources could handle invalid options better Change By: Branan Riley Story Points: 5 0 Sprint: Client 2016-07-13 (HA, 1.5.3), Client 2016-07-27, Client 2016-08-10, Client 2016-08-24, Client 2016-09-07 , APS 2016-09-21 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6457) Mount resources could handle invalid options better
Title: Message Title Branan Riley updated an issue Puppet / PUP-6457 Mount resources could handle invalid options better Change By: Branan Riley Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6457) Mount resources could handle invalid options better
Title: Message Title Branan Riley updated an issue Puppet / PUP-6457 Mount resources could handle invalid options better Change By: Branan Riley Sprint: Client 2016-07-13 (HA, 1.5.3), Client 2016-07-27, Client 2016-08-10, Client 2016-08-24, Client 2016-09-07 , Client 2016-09-21 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6457) Mount resources could handle invalid options better
Title: Message Title Branan Riley updated an issue Puppet / PUP-6457 Mount resources could handle invalid options better Change By: Branan Riley Team: Agent & Platform Support Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6697) Allow full downloaded CA bundle to be stored to agent's localcacert file
Title: Message Title
Jeremy Barlow updated an issue
Puppet / PUP-6697
Allow full downloaded CA bundle to be stored to agent's localcacert file
Change By:
Jeremy Barlow
If a bundle of CA certificates is stored where the CA service's {{cacert}} setting points (/etc/puppetlabs/puppet/ssl/ca/ca_crt.pem by default in Puppet 4.x / Puppet Server 2.x), Puppet Server's CA will send the full CA bundle to the agent when the agent requests them. The agent, however, will only store the first certificate from the bundle to its {{localcacert}} location - /etc/puppetlabs/puppet/ssl/certs/ca.pem by default in Puppet 4.x.After the agent certificate is signed by the CA, subsequent agent runs against the master could fail with an error like the following:{noformat}Error: Could not request certificate: SSL_connect returned=1 errno=0 state=error: certificate verify failed: [unable to get issuer certificate for /C=US/ST=Oregon/O=Puppet/CN=intermediateca.example.org/emailAddress=intermediat...@example.org]{noformat}The above error would happen for the case that the master's server certificate were issued by an intermediate CA and only the intermediate CA certificate were stored to the agent's {{localcacert}} file -- not the certificate of the issuing root CA.Effectively, then, in order for the master to use an intermediate CA certificate to issue agent certificates, one would apparently have to manually put the root + intermediate CA bundle in place at the agent's {{localcacert}} location since only one of the CA certificates from the bundle is stored to the {{localcacert}} as part of the agent run. It would seem better instead for the full CA certificate bundle to be stored to the agent's {{localcacert}} location.h5. Steps to Reproduce1) Install Puppet Server.2) Copy the attached ca_crl.pem, ca_crt.pem, and ca_key.pem files to the /etc/puppetlabs/puppet/ssl/ca directory.The “ca_crl.pem” and “ca_crt.pem” files contain CRL and CA PEMs for both the Root and Intermediate CAs, respectively. The “ca_key.pem” file contains the Intermediate CA’s private key.3) Add the following lines to the /etc/puppetlabs/puppet/puppet.conf file in order to workaround the lack of support for processing multiple CRL files per the CA certificate chain - see SERVER PUP - 1315 3788 :{noformat}[agent]certificate_revocation = false{noformat}3) Run the following command:{noformat}puppet cert generate `facter fqdn`{noformat}4) Start Puppet Server5) Do an agent run, targeting a unique ssl directory so that the CA cert and CRL which are downloaded will differ from those in the master ssl directory.{noformat}puppet agent -t --certname myagent --server `facter fqdn` --ssldir /tmp/myagent-ssl{noformat}The agent run should exit with a line indicating that the certificate needs to be signed.{noformat}Exiting; no certificate found and waitforcert is disabled{noformat}6) Sign the myagent certificate request.{noformat}puppet cert sign myagent{noformat}7) Repeat the previous agent run:{noformat}puppet agent -t --certname myagent --server `facter fqdn` --ssldir /tmp/myagent-ssl{noformat}h6. Expected:Agent run is successful, with no warnings.h6. Actual:An error message is displayed:{noformat}Error: Could not request certificate: SSL_connect returned=1 errno=0 state=error: certificate verify failed: [unable to
Jira (PUP-6698) Puppet server 2.5.0 does not properly handle exported file resources
Title: Message Title Kylo Ginsberg moved an issue Puppet / PUP-6698 Puppet server 2.5.0 does not properly handle exported file resources Change By: Kylo Ginsberg Affects Version/s: SERVER 2.5.0 Affects Version/s: SERVER 2.4.0 Affects Version/s: PUP 4.6.0 Key: SERVER PUP - 1495 6698 Project: Puppet Server Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe
Jira (PDB-3048) Add support for multiple puppetdb servers
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3048 Add support for multiple puppetdb servers Issue Type: Bug Assignee: Unassigned Created: 2016/09/12 10:42 AM Priority: Normal Reporter: gepetto-bot Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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
Jira (PDB-3048) Add support for multiple puppetdb servers
Title: Message Title gepetto-bot updated an issue PuppetDB / PDB-3048 Add support for multiple puppetdb servers Change By: gepetto-bot Sprint: EP 2016-09-21 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (PDB-3047) PDB Changes required for 'corrective change' in CM's Event Inspector
Title: Message Title Beth Cornils commented on PDB-3047 Re: PDB Changes required for 'corrective change' in CM's Event Inspector sweet! Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (HI-537) Default value doesn't work correctly with an alias
Title: Message Title Stephen Gelman commented on HI-537 Re: Default value doesn't work correctly with an alias I understand. As an aside that actually seems very useful for us and I am glad to know it is an option. Another fix I considered would be to pass the default value from lookup down into the recursive lookup. I believe that would avoid breaking automatic parameter lookup but it would require changing a number of function signatures. I know in the past that was a concern in hiera. Do you think that is a workable solution? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-1502) acceptance: mount a tmpfs directory and check the fact
Title: Message Title Kenn Hussey assigned an issue to Moses Mendoza Facter / FACT-1502 acceptance: mount a tmpfs directory and check the fact Change By: Kenn Hussey Assignee: Moses Mendoza Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6484) Productize Puppet lookup
Title: Message Title Craig Gomes updated an issue Puppet / PUP-6484 Productize Puppet lookup Change By: Craig Gomes Epic Name: Productize Puppet Lookup completers Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (PDB-3047) PDB Changes required for 'corrective change' in CM's Event Inspector
Title: Message Title Karel Brezina updated an issue PuppetDB / PDB-3047 PDB Changes required for 'corrective change' in CM's Event Inspector Change By: Karel Brezina Sprint: CR SCR 2016-09-21 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (PDB-3047) PDB Changes required for 'corrective change' in CM's Event Inspector
Title: Message Title Karel Brezina updated an issue PuppetDB / PDB-3047 PDB Changes required for 'corrective change' in CM's Event Inspector Change By: Karel Brezina Story Points: 5 Sprint: CR 2016-09-21 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (PDB-3047) PDB Changes required for 'corrective change' in CM's Event Inspector
Title: Message Title Steve Quin commented on PDB-3047 Re: PDB Changes required for 'corrective change' in CM's Event Inspector Beth Cornils This ticket is a must without the PDB changes we have no corrective change in EI. Also it fits under all the Story's you created, so I just linked it ot the epic. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-5834) Handle extended data in the catalog
Title: Message Title Henrik Lindberg commented on PUP-5834 Re: Handle extended data in the catalog Yes, although the Binary type was expected to be the first to trailblaze through. We could have done it with the regexp. The intent was though to get suppot for "new" and similar things from the Binary implementation. As it turned out we followed a slightly different track. The Binary is a good candidate to use since it should naturally be binary encoded when serialized in a binary format, and something like Base64 in a textual format. Using it as the model is therefore a good thing. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (PDB-3047) PDB Changes required for 'corrective change' in CM's Event Inspector
Title: Message Title Beth Cornils updated an issue PuppetDB / PDB-3047 PDB Changes required for 'corrective change' in CM's Event Inspector Change By: Beth Cornils Scrum Team: Change Reporting Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (PDB-3047) PDB Changes required for 'corrective change' in CM's Event Inspector
Title: Message Title Beth Cornils updated an issue PuppetDB / PDB-3047 PDB Changes required for 'corrective change' in CM's Event Inspector Change By: Beth Cornils Labels: security Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (PDB-3047) PDB Changes required for 'corrective change' in CM's Event Inspector
Title: Message Title Beth Cornils commented on PDB-3047 Re: PDB Changes required for 'corrective change' in CM's Event Inspector Steve Quin does that mean it's a stealth ticket we can just make happen? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-2769) specify how 4.x function api code can get caller / source location
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2769 specify how 4.x function api code can get caller / source location Change By: Henrik Lindberg Fix Version/s: PUP 4.y Fix Version/s: PUP 4.8.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-5834) Handle extended data in the catalog
Title: Message Title Thomas Hallgren commented on PUP-5834 Re: Handle extended data in the catalog Why is this ticket blocked by the Binary type specifically? Isn't this also needed to handle Regexp, Timespan, and Timestamp properly in the catalog? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6174) "Copy" variables from a class in the current scope
Title: Message Title Francois Lafont commented on PUP-6174 Re: "Copy" variables from a class in the current scope Late comment, but thanks for this very useful feature. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-5834) Handle extended data in the catalog
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-5834 Handle extended data in the catalog Change By: Thomas Hallgren Sprint: PDS Triage 2016-09-21 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-5834) Handle extended data in the catalog
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-5834 Handle extended data in the catalog Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-2769) specify how 4.x function api code can get caller / source location
Title: Message Title Henrik Lindberg commented on PUP-2769 Re: specify how 4.x function api code can get caller / source location The ability to get caller information has been added to puppet already as it was needed to fix issues with create_resources. The new PuppetStack needs to be specified and documented. It seems natural to add this to the 4.x function API specification. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-2769) specify how 4.x function api code can get caller / source location
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2769 specify how 4.x function api code can get caller / source location Change By: Henrik Lindberg Summary: new specify how 4.x function api should have a way to code can get caller / source location Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-1810) Deprecate referencing classes with an initial capital letter
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1810 Deprecate referencing classes with an initial capital letter Change By: Henrik Lindberg Sprint: PDS 2016-10-05 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (PDB-3047) PDB Changes required for 'corrective change' in CM's Event Inspector
Title: Message Title Karel Brezina assigned an issue to Karel Brezina PuppetDB / PDB-3047 PDB Changes required for 'corrective change' in CM's Event Inspector Change By: Karel Brezina Assignee: Karel Brezina Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (PDB-3047) PDB Changes required for 'corrective change' in CM's Event Inspector
Title: Message Title Steve Quin updated an issue PuppetDB / PDB-3047 PDB Changes required for 'corrective change' in CM's Event Inspector Change By: Steve Quin Acceptance Criteria: The required PuppetDB changes for 'corrective change' in CM's *Event Inspector* will be implenmented implemented to support PE-17254 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (PDB-3047) PDB Changes required for 'corrective change' in CM's Event Inspector
Title: Message Title Steve Quin commented on PDB-3047 Re: PDB Changes required for 'corrective change' in CM's Event Inspector Hi Nirupama Mantha cc Karel Brezina & Beth Cornils, This ticket is vital for all the corrective change work. I have added this to the backlog. However, I cant seem to work out how to add Security, Compliance & Reporting OR Change Reporting as a component? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6291) Add 'abs' support to Numeric.new
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-6291 Add 'abs' support to Numeric.new Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6291) Add 'abs' support to Numeric.new
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-6291 Add 'abs' support to Numeric.new Change By: Thomas Hallgren Sprint: PDS 2016- 10 09 - 05 21 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (PDB-3047) PDB Changes required for 'corrective change' in CM's Event Inspector
Title: Message Title Steve Quin updated an issue PuppetDB / PDB-3047 PDB Changes required for 'corrective change' in CM's Event Inspector Change By: Steve Quin Fix Version/s: pe everett Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (PDB-3047) PDB Changes required for 'corrective change' in CM's Event Inspector
Title: Message Title Steve Quin updated an issue PuppetDB / PDB-3047 PDB Changes required for 'corrective change' in CM's Event Inspector Change By: Steve Quin Fix Version/s: pe everett Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (PDB-3047) PDB Changes required for 'corrective change' in CM's Event Inspector
Title: Message Title Beth Cornils created an issue PuppetDB / PDB-3047 PDB Changes required for 'corrective change' in CM's Event Inspector Issue Type: Story Assignee: Unassigned Components: PuppetDB Created: 2016/09/12 5:45 AM Priority: Major Reporter: Beth Cornils To implement 'corrective change' in CM's Event Inspector there are changes required in PuppetDB. This ticket is to investigate and implement the 'corrective change' as detailed in PE-17254 Add Comment
Jira (PUP-2769) new function api should have a way to get caller / source location
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2769 new function api should have a way to get caller / source location Change By: Henrik Lindberg Sprint: PDS 2016-10-05 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6005) Specify the ordering used for directory based main manifest
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6005 Specify the ordering used for directory based main manifest Change By: Henrik Lindberg Sprint: PDS 2016-09-21 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6291) Add 'abs' support to Numeric.new
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6291 Add 'abs' support to Numeric.new Change By: Henrik Lindberg Sprint: PDS 2016-10-05 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-5908) Implement a PCore MsgPack Serializer
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5908 Implement a PCore MsgPack Serializer Change By: Henrik Lindberg Sprint: Language 2016-06-29 , PDS 2016-10-05 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-4742) Bring semantic_puppet library into Puppet
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4742 Bring semantic_puppet library into Puppet Change By: Henrik Lindberg Sprint: Language 2016-06-01, Language 2016-06-15, Language 2016-06-29 , PDS 2016-10-05 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6135) change type mismatch errors in past tense to present tense
Title: Message Title Henrik Lindberg commented on PUP-6135 Re: change type mismatch errors in past tense to present tense After a bit of discussion I think we concluded that we should say "expects" as that should work in all cases since they expectancy still exists in all cases. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6135) change type mismatch errors in past tense to present tense
Title: Message Title Thomas Hallgren commented on PUP-6135 Re: change type mismatch errors in past tense to present tense The description uses mixed tense in that 'has' is present tense, but 'expected' is past tense. I think that makes sense. It's however very common to use past tense overall. So while fixing this bug, do we want to consequently use mixed tense throughout with wording like "X has/Z returns/X references/ zzz, expected xxx, got yyy"? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-1506) sp_serial_number is empty on macOS Sierra (10.12)
Title: Message Title Daniele Sluijters commented on FACT-1506 Re: sp_serial_number is empty on macOS Sierra (10.12) It seems this only affects facter 3.3.x, I just upgraded to 3.4.1 and sp_serial_number shows up correctly now. Not entirely sure why just yet. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (HI-537) Default value doesn't work correctly with an alias
Title: Message Title
Henrik Lindberg commented on HI-537
Re: Default value doesn't work correctly with an alias
Earlier it was impossible to give an undef to a parameter via data binding in this situation:
class example($x) { }
include example If you set the value to some kind of nil in the data (depends on the file format/backend) the result was that puppet complained about a missing value since there is no default _expression_. If the key example::x is missing the result is "missing value" error. This now works in puppet and the value is set to undef. If however the example is written like this:
class example($x=42) { }
include example
Here the lookup of undef will select the default value (42).
In older versions of puppet, the only way to get an actual undef via data binding was to set it as the default value.
Add Comment
