Jira (PUP-6695) equality operation regression
Title: Message Title Curtis Ruck commented on PUP-6695 Re: equality operation regression So, this has been working stable since early 2015, and no changes have been made to these functions for a year. Looking at the release notes, it must have come with the update to JRuby somehow. I'll have to go through the rest of my modules to ensure we are not using symbols, we make heavy use of them in our custom types/providers instead of strings. For some reason I thought the equality operator did the to_s conversion, vice doing the 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-6596) Update CFPropertyList gem to 2.3.3 and add plain format to puppet/util/plist
Title: Message Title Samuel Keeley updated an issue Puppet / PUP-6596 Update CFPropertyList gem to 2.3.3 and add plain format to puppet/util/plist Change By: Samuel Keeley Summary: Update CFPropertyList gem to 2.3. 2 3 and add plain format to puppet/util/plist Puppet currently bundles version 2.2.7 of the CFPropertyList gem. This works fine, but the newest version 2.3. 2 3 has a couple of bug fixes and also adds support for the rare plain ASCII format. Having support for this format would be very useful in certain situations, as Xcode and System Profiler still use it. We've also recently discovered a serious bug in string handling, see PUP-6696. 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-1505) facter/util/plist mishandles long strings due to bug in CFPropertyList gem
Title: Message Title Samuel Keeley commented on FACT-1505 Re: facter/util/plist mishandles long strings due to bug in CFPropertyList gem Pull request https://github.com/puppetlabs/facter/pull/1420 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-1505) facter/util/plist mishandles long strings due to bug in CFPropertyList gem
Title: Message Title Samuel Keeley created an issue Facter / FACT-1505 facter/util/plist mishandles long strings due to bug in CFPropertyList gem Issue Type: Bug Affects Versions: FACT 2.4.6 Assignee: Unassigned Created: 2016/09/09 5:52 PM Priority: Normal Reporter: Samuel Keeley Please see PUP-6696 for more info; Facter 2 bundles CFPropertyList 2.2.7 which needs to be updated to 2.3.3 to fix this bug. Add Comment
Jira (PUP-6696) puppet/util/plist mishandles long strings due to bug in CFPropertyList gem
Title: Message Title Samuel Keeley created an issue Puppet / PUP-6696 puppet/util/plist mishandles long strings due to bug in CFPropertyList gem Issue Type: Bug Affects Versions: PUP 4.6.2 Assignee: Kylo Ginsberg Components: Types and Providers Created: 2016/09/09 5:50 PM Priority: Normal Reporter: Samuel Keeley Please see https://github.com/ckruse/CFPropertyList/issues/44 Puppet (and Facter 2) currently bundle CFPropertyList 2.2.7 which has a nasty bug that results in mishandled long strings in XML plists, reflowing them when it shouldn't be. This bug is fixed in version 2.3.3, which also adds support for plaintext plists. Add Comment
Jira (PUP-6695) equality operation regression
Title: Message Title Henrik Lindberg commented on PUP-6695 Re: equality operation regression We decided a long time ago to not transform the values returned from functions because of the performance cost as we would need to recursively transform every array and hash. It is the responsibility of the implementor of a function to only return Ruby objects that are supported by the Puppet Language. Ruby Symbol is not one of them. We should check that the specification clearly states this (if it is not already stated). The fact that the example worked in an older version of puppet is pure coincidence, probably because of the monkey patch that equates symbols with strings. That monkeypatch causes other bugs, and we therefore started to be super sensitive about how we compare to avoid the monkey patch kicking in where it should not. I think the functions should be changed to use Strings. That should also be backwards compatible. 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-3046) (maint) Update PDB to use new signing key
Title: Message Title gepetto-bot updated an issue PuppetDB / PDB-3046 (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-3046) (maint) Update PDB to use new signing key
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3046 (maint) Update PDB to use new signing key Issue Type: Bug Assignee: Unassigned Created: 2016/09/09 2:47 PM 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-3045) puppetdb module does not allow the use of puppetserver with puppet 3x and puppetdb 2x
Title: Message Title
Eric Thompson created an issue
PuppetDB / PDB-3045
puppetdb module does not allow the use of puppetserver with puppet 3x and puppetdb 2x
Issue Type:
Bug
Assignee:
Unassigned
Created:
2016/09/09 2:44 PM
Priority:
Normal
Reporter:
Eric Thompson
https://github.com/puppetlabs/puppetlabs-puppetdb/blob/master/manifests/params.pp#L71 TL;DR:
if !($puppetdb_version in ['latest','present','absent']) and versioncmp($puppetdb_version, '3.0.0') < 0 {
case $::osfamily {
'RedHat', 'Suse', 'Archlinux','Debian': {
Jira (PUP-6695) equality operation regression
Title: Message Title Thomas Hallgren commented on PUP-6695 Re: equality operation regression When I run the manifest from the base64 encoded tar image, I get the following output: Notice: simple: a is present Notice: /Stage[main]/Main/Notify[simple: a is present]/message: defined 'message' as 'simple: a is present' Notice: simple: b is present Notice: /Stage[main]/Main/Notify[simple: b is present]/message: defined 'message' as 'simple: b is present' This is consistent with the bug report. If I then change the return values of the #ensure function from symbols to strings, I instead get: Notice: simple: a is present Notice: /Stage[main]/Main/Notify[simple: a is present]/message: defined 'message' as 'simple: a is present' Notice: simple: b is present Notice: /Stage[main]/Main/Notify[simple: b is present]/message: defined 'message' as 'simple: b is present'
Jira (PUP-6695) equality operation regression
Title: Message Title Henrik Lindberg commented on PUP-6695 Re: equality operation regression Note that functions should not return Ruby Symbol to the Puppet Language. The only supported symbol is :undef - all other symbols returned to the puppet language are subject to undefined behavior. The examples return :present and :absent - they should return strings 'present' and 'absent'. 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 merged up to master at v 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 Merged to stable at https://github.com/puppetlabs/puppet/commit/4ba3fd57d77e18c8c635a92f76e6a45feb49fbc6 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 Glenn Sarti assigned an issue to Moses Mendoza Puppet / PUP-6641 Integration test for Windows service fails on Windows 10 Change By: Glenn Sarti 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-6641) Integration test for Windows service fails on Windows 10
Title: Message Title Glenn Sarti assigned an issue to Glenn Sarti Puppet / PUP-6641 Integration test for Windows service fails on Windows 10 Change By: Glenn Sarti Assignee: Moses Mendoza Glenn Sarti 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-6670) Newlines break Puppet tag validation
Title: Message Title Branan Riley commented on PUP-6670 Re: Newlines break Puppet tag validation Pulled this into our sprint and marked it blocked. This is all set for Sean McDonald to pick up when he's done with the 4.7.0 stuff 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-6670) Newlines break Puppet tag validation
Title: Message Title Branan Riley updated an issue Puppet / PUP-6670 Newlines break Puppet tag validation Change By: Branan Riley Sprint: Language 2016-09-07, PDS 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-6670) Newlines break Puppet tag validation
Title: Message Title Branan Riley assigned an issue to Sean McDonald Puppet / PUP-6670 Newlines break Puppet tag validation Change By: Branan Riley Assignee: Sean McDonald Team: Agent & Platform Support Scrum Team: Language 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-6670) Newlines break Puppet tag validation
Title: Message Title Branan Riley commented on PUP-6670 Re: Newlines break Puppet tag validation I've updated the fix version to 4.7.1, and bumped this back to "Ready for Engineering". Once we tag 4.7.0 we'll revert the revert and get this back in for the next Z 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-6670) Newlines break Puppet tag validation
Title: Message Title Branan Riley updated an issue Puppet / PUP-6670 Newlines break Puppet tag validation Change By: Branan Riley Fix Version/s: PUP 4.6.3 Fix Version/s: PUP 4.7.1 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-6695) equality operation regression
Title: Message Title Curtis Ruck commented on PUP-6695 Re: equality operation regression Due to my environment it is significantly harder to get my test case files (but i can copy+paste) out, so here is a Base64 encoded Tar archive/Gzip compressed. Can be extracted with cat << EOF | base64 -d | tar -zxv H4sIADXf0lcAA+1ZS2/bRhBWeyTQ/zBwYsgu9OCbAIEeihQ59RAghxyiIFiSo2phcklwl40Fw0B+ UX9jZklKthQ4ekSiYZTfReLsY0b85pt9SKFUCS+ngzPCJASeOfhK3+W73/5rPn/9xXzAwLID3/U8 03L9gWk5vm0OwDtnUCtUUrESYBCXVXwzSdhT/ZI8Y1xAJbGUXcTVEVTL/4Jjyc6UBfvz7waBZRH/ bmC5Pf9dYJN//TRZsiw9qQ9NsO/+gH/bWfPvBS7x73u+PQDzpFE8gf85/3Nkqirxs2Y+BFVWaDx3 SD06xIb+Ty/9Grv079neev0n7ZP+PS9wev13gfF4bIQRi29QJDI0AMagk8AI64Qo48WyMeo8MYxQ t4XGK0iYYpQ2wCVgVqglLLDEEcgc6nH6NUngSkKCc1alSupBY5iiiqdFVRSoUhbJaZwnOEXxLy9z kaFQcnp59+jxvklL7QxyAb8LfltPc/kmz7Jc/FkUf1HT5exdPePfNONMzzh7PONsc8bZxowfuEjy L5Im/bBAAbLAmM+XXPwDbPUTR5CxGwRJRRLUAoFMGKu8XALecqnkhF5P2PYNm1//kiroSv9ZnlQp
Jira (PUP-6670) Newlines break Puppet tag validation
Title: Message Title Sean McDonald commented on PUP-6670 Re: Newlines break Puppet tag validation Henrik Lindberg Charlie Sharpsteen This commit has been removed from stable, as we need the 4.7.0 release to be as small as possible from a component standpoint (since we are updating to a new ruby) /cc Geoff Nichols Branan Riley 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-6695) equality operation regression
Title: Message Title Curtis Ruck created an issue Puppet / PUP-6695 equality operation regression Issue Type: Bug Affects Versions: PUP 4.6.2 Assignee: Unassigned Components: Language Created: 2016/09/09 9:10 AM Environment: Pupppet Agent 1.6.2, Puppet Server 2.6.0, unchanged manifests for over a year and originally written on Puppet Agent 4.0 and Puppet Server 2.0 Priority: Blocker Reporter: Curtis Ruck It appears that the symbol to string conversion for the equality operator in the puppet language has broken. We only noticed this when Puppet Server 2.6.0 came in this morning, but have recreated it with a puppet apply command. Essentially, we have puppet functions that lookup hiera boolean values, and return ensure symbols such as present, absent. In the below sample, we receive this output, but we used to receive "complex: b is present" hiera's yaml
Jira (PUP-6592) acceptance: Sensitive data
Title: Message Title William Hopper assigned an issue to William Hopper Puppet / PUP-6592 acceptance: Sensitive data Change By: William Hopper Assignee: William Hopper 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-6686) Timespan sometimes parses fractions incorrectly.
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-6686 Timespan sometimes parses fractions incorrectly. Change By: Henrik Lindberg Assignee: Henrik Lindberg 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 Thomas Hallgren commented on PUP-4742 Re: Bring semantic_puppet library into Puppet Kylo Ginsberg, is this ticket still blocked or are the msi's built? 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 Thomas Hallgren commented on PUP-5908 Re: Implement a PCore MsgPack Serializer Kylo Ginsberg, Is the blocking work on this resolved (seems like it, since the blocker is closed). If so, is it OK to merge the PR? 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-6685) Remove underscore from Timespan/Timestamp milli_seconds, micro_seconds, and nano_seconds
Title: Message Title Henrik Lindberg commented on PUP-6685 Re: Remove underscore from Timespan/Timestamp milli_seconds, micro_seconds, and nano_seconds merged to master at: e19b9f1 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 updated an issue Puppet / PUP-6135 change type mismatch errors in past tense to present tense 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-6692) Improve access to "master" settings
Title: Message Title Henrik Lindberg commented on PUP-6692 Re: Improve access to "master" settings One idea that was floated is that $server_facts should be used, and that settings would be a key in that hash. That is unfortunately not possible (or will create a mess) as the server facts are merged into the node facts - thus creating a confusion over where values comes from (agent/server) - this is already confusing as it is. So, that idea is scrapped. 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 assigned an issue to Thomas Hallgren Puppet / PUP-6135 change type mismatch errors in past tense to present tense 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-6694) The Puppet Data type should be limited to JSON types.
Title: Message Title Henrik Lindberg commented on PUP-6694 Re: The Puppet Data type should be limited to JSON types. This means that we may want to also address where Data is used as a default parameter value. 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-6693) Warn/error if $trusted_server_data is assigned if not in --trusted_server_facts mode and --strict is on
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-6693 Warn/error if $trusted_server_data is assigned if not in --trusted_server_facts mode and --strict is on 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-6693) Warn/error if $trusted_server_data is assigned if not in --trusted_server_facts mode and --strict is on
Title: Message Title Thomas Hallgren commented on PUP-6693 Re: Warn/error if $trusted_server_data is assigned if not in --trusted_server_facts mode and --strict is on Merged to master at bf1e560. 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-6693) Warn/error if $trusted_server_data is assigned if not in --trusted_server_facts mode and --strict is on
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-6693 Warn/error if $trusted_server_data is assigned if not in --trusted_server_facts mode and --strict is on 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-1581) Agent settings should be available within the parser
Title: Message Title Henrik Lindberg commented on PUP-1581 Re: Agent settings should be available within the parser Since this was first reported, some settings are available as facts. The best option seems to be to simply add the settings that are of importance as additional facts. Selecting a few seems best as adding all settings under a 'settings' fact may be overkill and just waste performance and memory. Note that in PUP-6692, it is suggested that the "master" settings are added under $server_facts as 'settings'. Doing the same for facts from a node would make the support symmetrical. 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-6694) The Puppet Data type should be limited to JSON types.
Title: Message Title Thomas Hallgren created an issue Puppet / PUP-6694 The Puppet Data type should be limited to JSON types. Issue Type: Bug Assignee: Unassigned Created: 2016/09/09 5:45 AM Fix Versions: PUP 5.0.0 Priority: Normal Reporter: Thomas Hallgren The motivation behind the Data type is that instances of this type can be presented as JSON without conversion. As such, it must only represent the following: Data |- Boolean |- Numeric
Jira (PUP-6693) Warn/error if $trusted_server_data is assigned if not in --trusted_server_facts mode and --strict is on
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-6693 Warn/error if $trusted_server_data is assigned if not in --trusted_server_facts mode and --strict is on Change By: Henrik Lindberg Assignee: Henrik Lindberg 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-6693) Warn/error if $trusted_server_data is assigned if not in --trusted_server_facts mode and --strict is on
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-6693 Warn/error if $trusted_server_data is assigned if not in --trusted_server_facts mode and --strict is on Issue Type: Bug Assignee: Unassigned Created: 2016/09/09 5:20 AM Priority: Normal Reporter: Henrik Lindberg We are planning to throw the switch on --trusted_server_data in Puppet 5.0.0 (PUP-6612). The current implementation does however not issue a deprecation warning for an assignment to $server_facts and it would then simply error on 5.0.0. To make that better, we can use --strict to control if assignment to $server_facts should be a warning, error, or be ignored. That gives users a chance to fix this before they upgrade. Add Comment
Jira (PUP-6692) Improve access to "master" settings
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-6692
Improve access to "master" settings
Change By:
Henrik Lindberg
Currently, there is a namespace {{settings}} in which all settings are set as individual variables. This makes them harder to use as the available settings change between versions, and using strict variables can cause errors, and the available settings cannot be enumerated. Having a {{$settings}} as a hash of all settings is also desirable, and is analog to how {{$facts}} work.Note that PUP-1581 is about making possible to also access the settings from a node. That complicates this ticket with having to take future agent settings into account when designing how the improved access should be done. The settings for the compiling runtime (in master mode, or when doing a puppet apply) is what is currently reflected in {{settings}}. When designing the support for {{$settings}}, is that a good name for the variable? What should the variable for the "node settings" be? Should we use "local" and "node" as subkeys - that is {{$settings\[local]}} is what we have now, and {{$settings\[node]}} what will be added in PUP-1581, or should we have two global variables? We could also keep the existing namespace, so that {{$settings::local}} and {{$settings::node}} (or the asymmetrical {{$settings}} and {{$settings::node}}).If we use the existing namespace, support for this can be added in 4.x. If we go for that option, the two sections "local" and "node" will need to coexist with all the existing settings, and thus those names cannot be used as new settings (they are not used now).Another alternative is to add a function {{settings(name)}} which would return a setting or an Iterable over all settings if not given a name. This would reduce the amount of data kept in memory (there are many settings, and only a few of them, if any) are ever used in manifests. The return of an iterable means that the settings can be efficiently iterated (without first having to create a hash copy).We could also bind the Iterable to $settings, as that would be the most efficient, as the result is almost indistinguishable from a Hash.
Add Comment
Jira (PUP-6692) Improve access to "master" settings
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-6692
Improve access to "master" settings
Change By:
Henrik Lindberg
Currently, there is a namespace {{settings}} in which all settings are set as individual variables. This makes them harder to use as the available settings change between versions, and using strict variables can cause errors, and the available settings cannot be enumerated. Having a {{$settings}} as a hash of all settings is also analog to how {{$facts}} work.Note that PUP-1581 is about making possible to also access the settings from a node. That complicates this ticket with having to take future agent settings into account when designing how the issue improved access should be done . The settings for the compiling runtime (in master mode, or when doing a puppet apply) is what is currently reflected in {{settings}}. When designing the support for {{$settings}}, is that a good name for the variable? What should the variable for the "node settings" be? Should we use "local" and "node" as subkeys - that is {{$settings\[local]}} is what we have now, and {{$settings\[node]}} what will be added in PUP-1581, or should we have two global variables? We could also keep the existing namespace, so that {{$settings::local}} and {{$settings::node}} (or the asymmetrical {{$settings}} and {{$settings::node}}).If we use the existing namespace , support for this can be added in 4.x. If we go for that option, the two sections "local" and "node" will need to coexist with all the existing settings, and thus those names cannot be used as new settings (they are not used now).Another alternative is to add a function {{settings(name)}} which would return a setting or an Iterable over all settings if not given a name. This would reduce the amount of data kept in memory (there are many settings, and only a few of them, if any) are ever used in manifests. The return of an iterable means that the settings can be efficiently iterated (without first having to create a hash copy).We could also bind the Iterable to $settings, as that would be the most efficient, as the result is almost indistinguishable from a Hash.
Add Comment
Jira (PUP-6682) $settings leaks symbols into manifests
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-6682 $settings leaks symbols into manifests Change By: Thomas Hallgren Assignee: Henrik Lindberg 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-6682) $settings leaks symbols into manifests
Title: Message Title Thomas Hallgren commented on PUP-6682 Re: $settings leaks symbols into manifests Merged to master at efb3639. 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-6692) Improve access to "master" settings
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-6692
Improve access to "master" settings
Change By:
Henrik Lindberg
Currently, there is a namespace {{settings}} in which all settings are set as individual variables. This makes them harder to use as the available settings change between versions, and using strict variables can cause errors, and the available settings cannot be enumerated. Having a {{$settings}} as a hash of all settings is also analog to how {{$facts}} work.Note that PUP-1581 is about making possible to also access the settings from a node. That complicates the issue. The settings for the compiling runtime (in master mode, or when doing a puppet apply) is what is currently reflected in {{settings}}. When designing the support for {{$settings}}, is that a good name for the variable? What should the variable for the "node settings" be? Should we use "local" and "node" as subkeys - that is {{$settings\[local]}} is what we have now, and {{$settings\[node]}} what will be added in PUP-1581, or should we have two global variables? We could also keep the existing namespace, so that {{$settings::local}} and {{$settings::node}} (or the asymmetrical {{$settings}} and {{$settings::node}}).If we use the existing namespace support for this can be added in 4.x. If we go for that option, the two sections "local" and "node" will need to coexist with all the existing settings, and thus those names cannot be used as new settings (they are not used now).Another alternative is to add a function {{settings(name)}} which would return a setting or an Iterable over all settings if not given a name. This would reduce the amount of data kept in memory (there are many settings, and only a few of them, if any) are ever used in manifests. The return of an iterable means that the settings can be efficiently iterated (without first having to create a hash copy). We could also bind the Iterable to $settings, as that would be the most efficient, as the result is almost indistinguishable from a Hash.
Add Comment
Jira (PUP-6692) Improve access to "master" settings
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6692 Improve access to "master" settings Change By: Henrik Lindberg Sprint: PDS Triage 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-6692) Improve access to "master" settings
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-6692 Improve access to "master" settings Issue Type: Improvement Assignee: Unassigned Created: 2016/09/09 3:59 AM Priority: Normal Reporter: Henrik Lindberg Currently, there is a namespace settings in which all settings are set as individual variables. This makes them harder to use as the available settings change between versions, and using strict variables can cause errors, and the available settings cannot be enumerated. Having a $settings as a hash of all settings is also analog to how $facts work. Note that PUP-1581 is about making possible to also access the settings from a node. That complicates the issue. The settings for the compiling runtime (in master mode, or when doing a puppet apply) is what is currently reflected in settings. When designing the support for $settings, is that a good name for the variable? What should the variable for the "node settings" be? Should we use "local" and "node" as subkeys - that is $settings[local] is what we have now, and $settings[node] what will be added in PUP-1581, or should we have two global variables? We could also keep the existing namespace, so that $settings::local and $settings::node (or the asymmetrical $settings and $settings::node). If we use the existing namespace support for this can be added in 4.x. If we go for that option, the two sections "local" and "node" will need to coexist with all the existing settings, and thus those names cannot be used as new settings (they are not used now). Another alternative is to add a function settings(name) which would return a setting or an Iterable over all settings if not given a name. This would reduce the amount of data kept in memory (there are many settings, and only a few of them, if any) are ever used in manifests. The return of an iterable means that the settings can be efficiently
Jira (PUP-6682) $settings leaks symbols into manifests
Title: Message Title Thomas Hallgren assigned an issue to Henrik Lindberg Puppet / PUP-6682 $settings leaks symbols into manifests Change By: Thomas Hallgren Assignee: Thomas Hallgren Henrik Lindberg 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-6289) Puppet 4.4.2 detects samba3x-common incorrect
Title: Message Title
Stefan Heijmans commented on PUP-6289
Re: Puppet 4.4.2 detects samba3x-common incorrect
Did a test with puppet 4.6 2 which still has the same behaviour.
$ puppet --version
4.6.2
$ rpm -qa|grep samba|sort
samba3x-3.6.23-9.el5_11
samba3x-client-3.6.23-9.el5_11
samba3x-common-3.6.23-9.el5_11
samba3x-winbind-3.6.23-9.el5_11
$ puppet resource package samba-common
package { 'samba-common':
ensure => '3.6.23-9.el5_11',
}
