Jira (PUP-1548) Facter deliver wrong architecture to puppet
Title: Message Title
Bjoern commented on an issue
Re: Facter deliver wrong architecture to puppet
Yes, of course.
Thanks
Add Comment
Puppet / PUP-1548
Facter deliver wrong architecture to puppet
I got this params.pp {noformat} case $::operatingsystem{ 'Debian', 'Ubuntu': { $package_name = SnareLinux-3.0.0-2_$::architecture.deb $provider = 'dpkg' $install_name = 'snarelinux' } {noformat} On Ubuntu Client puppet says: {noformat} root@PC3214ub:~# puppet agent -t info: Retrieving plugin ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2846) multiple providers are executed for the same resource
Title: Message Title cristi falcas updated an issue Puppet / PUP-2846 multiple providers are executed for the same resource Change By: cristi falcas Attachment: aws_securitygroup.rb Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2846) multiple providers are executed for the same resource
Title: Message Title cristi falcas commented on an issue Re: multiple providers are executed for the same resource I have attached the stub I'm using to test amazon security group provider. Add Comment Puppet / PUP-2846 multiple providers are executed for the same resource Hello, I'm trying to make a new provider for the firewall type, for amazon security groups. But I'm trying to use both providers inside the catalog: some rules I need for iptables only (for ex. nat rules), others for the security groups only. I'm differentiating between the rules with a special tag. I have only one class with something like this:... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2454) User ID's below 1000, not 500, are generally considered system users on OpenBSD
Title: Message Title Daniele Sluijters commented on an issue Re: User ID's below 1000, not 500, are generally considered system users on OpenBSD The 'correct' way to fix this on most Linux systems would be to read /etc/login.defs and look at the UID_MIN entry. Everything below UID_MIN is system user. Add Comment Puppet / PUP-2454 User ID's below 1000, not 500, are generally considered system users on OpenBSD Users can still modify this with 'uid_start' in adduser.conf, but in that case they'd need to provide an actual value instead of 'true'. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2691) Real-world module skeletons still use the 'description' metadata property
Title: Message Title
Ethan Brown commented on an issue
Re: Real-world module skeletons still use the 'description' metadata property
Merged into master at https://github.com/puppetlabs/puppet/commit/493119f3bbd61f6276951ef38da45eb0f0adfccb
Add Comment
Puppet / PUP-2691
Real-world module skeletons still use the 'description' metadata property
As per https://github.com/garethr/puppet-module-skeleton/issues/13 Changes to the way modules are generated in Puppet 3.6 mean that where users could previously rely on the presence of certain absent properties, they no longer can. The most prevalent example of this is the {{description}} property –including a template in your module skeleton which d...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1281) Remove win32console gem in ruby 2.0 on windows
Title: Message Title Ethan Brown commented on an issue Re: Remove win32console gem in ruby 2.0 on windows Yeah, this one is going to be tricky.. I also noticed that in my Ruby 2.0 x64 branch that we get a bunch of tests fails on the output comparison, where we get colored vs not-colored output now. Add Comment Puppet / PUP-1281 Remove win32console gem in ruby 2.0 on windows Ruby 2.0 on windows supports ANSI escape sequences, so the win32console gem is unnecessary. Also, ruby 2.0 likely support unicode character output correctly (such as the unicode box characters used in module tool output), so the windows-specific code in `lib/puppet/util/colors.rb` to force wide character output can be removed. See https://github.com/l... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-2521) Remove windows-pr gem as a Windows dependency
Title: Message Title Ethan Brown commented on an issue Re: Remove windows-pr gem as a Windows dependency Phase 2 is removing the gem from the gemspec and project_data.yaml. This is blocked on getting all the other gems updated to FFI versions that no longer depend on windows-pr. Add Comment Puppet / PUP-2521 Remove windows-pr gem as a Windows dependency The scope of this is unknown at this point, but it appears to be rather large. We currently use native Windows API calls defined in the windows-pr gem. Unfortunately, an FFI version of windows-pr was never released, and therefore the calls we directly make use of are *not* FFI'd. As such they will need replacement in preparation for x64. A more ex... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-392) Validate win32 gems on x86 and x64
Title: Message Title
Ethan Brown commented on an issue
Re: Validate win32 gems on x86 and x64
When upgrading win32-eventlog, note that these constants have changed names
Win32::EventLog::INFO - Win32::EventLog::INFO_TYPE
Win32::EventLog::ERR - Win32::EventLog::ERROR_TYPE Win32::EventLog::ERROR - Win32::EventLog::ERROR_TYPE
Win32::EventLog::WARN - Win32::EventLog::WARN_TYPE
Add Comment
Puppet / PUP-392
Validate win32 gems on x86 and x64
Some of the win32 gems that we use contain native code and are not portable to x64. The complete list of gems that we currently vendor is: https://github.com/puppetlabs/puppet-win32-ruby/tree/1.9.3/ruby/lib/ruby/gems/1.9.1/specifications {noformat} bigdecimal-1.1.0 deep_merge-1.0.0 ffi-1.9.0-x86-mingw32 io-console-0.3 json-1.5.5 minitar-0.5.4 mi...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2846) multiple providers are executed for the same resource
Title: Message Title Felix Frank assigned an issue to Felix Frank Puppet / PUP-2846 multiple providers are executed for the same resource Change By: Felix Frank Assignee: FelixFrank Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2852) puppet agent sign {hostname} silently works
Title: Message Title
Branson Matheson created an issue
Puppet / PUP-2852
puppet agent sign {hostname} silently works
Issue Type:
Improvement
Affects Versions:
3.6.2
Assignee:
Kylo Ginsberg
Components:
Client
Created:
27/Jun/14 5:54 AM
Priority:
Normal
Reporter:
Branson Matheson
This is more an annoyance .. however I believe the behavior should be modified to throw an error when there are invalid options on the command line. Especially given it's for Reliability.
puppet agent [--certname name] [-D|--daemonize|--no-daemonize] [-d|--debug] [--detailed-exitcodes] [--digest digest] [--disable] [--enable] [--fingerprint] [-h|--help] [-l|--logdest syslog|file|console] [--no-client] [--noop] [-o|--onetime] [--serve handler] [-t|--test] [-v|--verbose] [-V|--version] [-w|--waitforcert seconds]
There's no option 'sign' there
Jira (PUP-1852) deprecate the 'search' function
Title: Message Title Charlie Sharpsteen assigned an issue to Charlie Sharpsteen Puppet / PUP-1852 deprecate the 'search' function Change By: Charlie Sharpsteen Assignee: CharlieSharpsteen Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2454) User ID's below 1000, not 500, are generally considered system users on OpenBSD
Title: Message Title Peter Huene commented on an issue Re: User ID's below 1000, not 500, are generally considered system users on OpenBSD Daniele Sluijters Thanks, I didn't know about the existence of that file . That doesn't help us with the BSDs it seems, but it certainly couldn't hurt to try to read UID_MIN from it for correct behavior on various distros. I'll put up a PR to fix this. Add Comment Puppet / PUP-2454 User ID's below 1000, not 500, are generally considered system users on OpenBSD Users can still modify this with 'uid_start' in adduser.conf, but in that case they'd need to provide an actual value instead of 'true'. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1811) in with regexps should set match variables
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-1811 in with regexps should set match variables Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2853) Class default parameter true not overriden by Hiera
Title: Message Title Pedro Gonzlez created an issue Puppet / PUP-2853 Class default parameter true not overriden by Hiera Issue Type: Bug Affects Versions: 3.6.2 Assignee: Unassigned Created: 27/Jun/14 9:59 AM Environment: Debian Wheezy Priority: Normal Reporter: Pedro Gonzlez I'm experiencing the exact behaviour described on https://projects.puppetlabs.com/issues/17474#note-3 which is supposed to be fixed Add Comment
Jira (PUP-2104) Make puppet able to configure a facter implementation to use
Title: Message Title Adrien Thebo commented on an issue Re: Make puppet able to configure a facter implementation to use Merged in 338db55. Add Comment Puppet / PUP-2104 Make puppet able to configure a facter implementation to use This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2454) User ID's below 1000, not 500, are generally considered system users on OpenBSD
Title: Message Title Daniele Sluijters commented on an issue Re: User ID's below 1000, not 500, are generally considered system users on OpenBSD Peter Huene Awesome! I ran into this exact issue today. Add Comment Puppet / PUP-2454 User ID's below 1000, not 500, are generally considered system users on OpenBSD Users can still modify this with 'uid_start' in adduser.conf, but in that case they'd need to provide an actual value instead of 'true'. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-601) For /reports query operator should be optional
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-601 For /reports query operator should be optional Change By: Wyatt Alt Sprint: 20140507to20140521 ,20140618to20140702 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2817) Solaris Zone properties ip, dataset and inherit are not set upon zone creation
Title: Message Title Nick Walker updated an issue Puppet / PUP-2817 Solaris Zone properties ip, dataset and inherit are not set upon zone creation Change By: Nick Walker Labels: customersolaris support type_zone Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1811) in with regexps should set match variables
Title: Message Title
Andy Parker updated an issue
Puppet / PUP-1811
in with regexps should set match variables
Change By:
Andy Parker
{noformat} if/ . (a)/in[b,c,baba]{ notice($0) notice($1) } {noformat} resultsin baba ba andabeingoutput.
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PDB-601) For /reports query operator should be optional
Title: Message Title Wyatt Alt assigned an issue to Wyatt Alt PuppetDB / PDB-601 For /reports query operator should be optional Change By: Wyatt Alt Assignee: WyattAlt Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1811) in with regexps should set match variables
Title: Message Title
Andy Parker commented on an issue
Re: in with regexps should set match variables
Added PR 3 for the specification to update it to have this functionality.
Add Comment
Puppet / PUP-1811
in with regexps should set match variables
{noformat} if /.(a)/ in [b, c, baba] { notice($0) notice($1) } {noformat} results in ba and a being output.
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1811) in with regexps should set match variables
Title: Message Title Andy Parker assigned an issue to Henrik Lindberg Henrik Lindberg, I'm assigning this to you to take a look at the specification changes. Puppet / PUP-1811 in with regexps should set match variables Change By: Andy Parker Assignee: AndyParker HenrikLindberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-571) Error messages with IPv6-enabled interfaces.
Title: Message Title
Adrien Thebo updated an issue
Facter / FACT-571
Error messages with IPv6-enabled interfaces.
Change By:
Adrien Thebo
pre {noformat} cabbage~#facter--puppetnosuchfiletoload--ldapifconfig:status:SIOCGLIFFLAGS:bge0:1:nosuchinterfaceifconfig:status:SIOCGLIFFLAGS:bge0:1:nosuchinterfaceifconfig:status:SIOCGLIFFLAGS:bge0:1:nosuchinterfaceifconfig:status:SIOCGLIFFLAGS:bge0:1:nosuchinterfaceifconfig:status:SIOCGLIFFLAGS:bge0:1:nosuchinterface /pre {noformat} AworkaroundwouldbetoskiptheIPv6interfacenames: pre { code class=diff } index9fb7034..748bb1d100644---a/lib/facter/util/ip.rb+++b/lib/facter/util/ip.rb@@-59,7+59,7@@moduleFacter::Util::IPwhen'Linux','OpenBSD','NetBSD','FreeBSD','Darwin'output=%x{/sbin/ifconfig-a}when'SunOS'-output=%x{/usr/sbin/ifconfig-a}+output=%x{/usr/sbin/ifconfig-a4}endoutputend / { code /pre }
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2654) label provider for class/define should capitalize all segments
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-2654 label provider for class/define should capitalize all segments Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1811) in with regexps should set match variables
Title: Message Title
Andy Parker commented on an issue
Re: in with regexps should set match variables
Merged changes into puppet's master branch in baea55
Add Comment
Puppet / PUP-1811
in with regexps should set match variables
{noformat} if /.(a)/ in [b, c, baba] { notice($0) notice($1) } {noformat} results in ba and a being output.
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (FACT-345) IPv6 - interface missing
Title: Message Title Adrien Thebo commented on an issue Re: IPv6 - interface missing FACT-605 duplicates this issue but has more information and steps to fix than this issue, so I'm closing this issue as a duplicate in favor of FACT-605. Add Comment Facter / FACT-345 IPv6 - interface missing The IPv6 address facts are inconsistent: not all interfaces get a ipaddress6_interface fact. In my case I have eth0 and eth1, both with IP addresses, but facter creates facts ipaddress6_eth0 and ipaddress6 (with eth1's address). There should be an ipaddress_eth1 fact too. If I add a second IPv6 address to an interface the behavior is even more ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2741) remove the 'search' function
Title: Message Title Charlie Sharpsteen assigned an issue to Charlie Sharpsteen Puppet / PUP-2741 remove the 'search' function Change By: Charlie Sharpsteen Assignee: CharlieSharpsteen Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-345) IPv6 - interface missing
Title: Message Title Adrien Thebo commented on an issue Re: IPv6 - interface missing On closer inspection this looks related but not identical, so I've reopened this issue. However to fully reproduce it we need the version of ifconfig/net-tools that demonstrates this issue as well as a fully copy of the output of `ifconfig` to properly nail down the problem and fix. Add Comment Facter / FACT-345 IPv6 - interface missing The IPv6 address facts are inconsistent: not all interfaces get a ipaddress6_interface fact. In my case I have eth0 and eth1, both with IP addresses, but facter creates facts ipaddress6_eth0 and ipaddress6 (with eth1's address). There should be an ipaddress_eth1 fact too. If I add a second IPv6 address to an interface the behavior is even more ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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
Jira (PUP-2854) Puppet module build fails with no output
Title: Message Title Alex Dreyer updated an issue Puppet / PUP-2854 Puppet module build fails with no output Change By: Alex Dreyer Component/s: PMT Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2854) Puppet module build fails with no output
Title: Message Title Alex Dreyer created an issue Puppet / PUP-2854 Puppet module build fails with no output Issue Type: Bug Assignee: Alex Dreyer Created: 27/Jun/14 12:05 PM Priority: Normal Reporter: Alex Dreyer reported by Odeon in #puppet. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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,
Jira (PUP-2854) Puppet module build fails with no output
Title: Message Title Alex Dreyer updated an issue Puppet / PUP-2854 Puppet module build fails with no output Change By: Alex Dreyer reportedbyOdeonin#puppet. Puppetversion3.4.3 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2854) Puppet module build fails with no output
Title: Message Title Alex Dreyer commented on an issue Re: Puppet module build fails with no output Can't replicate with http://pastebin.com/VCmcM9Ea and puppet 3.4.3. Waiting on information. Add Comment Puppet / PUP-2854 Puppet module build fails with no output reported by Odeon in #puppet. Puppet version 3.4.3 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1811) in with regexps should set match variables
Title: Message Title
Henrik Lindberg commented on an issue
Re: in with regexps should set match variables
Spec change merged
Add Comment
Puppet / PUP-1811
in with regexps should set match variables
{noformat} if /.(a)/ in [b, c, baba] { notice($0) notice($1) } {noformat} results in ba and a being output.
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (FACT-605) facter ignores RFC 4193 ULAs when creating interface-specific ipaddress6 facts
Title: Message Title
Adrien Thebo commented on an issue
Re: facter ignores RFC 4193 ULAs when creating interface-specific ipaddress6 facts
What version of Ruby are you using with Facter? Could you provide the expected values of the missing facts?
Add Comment
Facter / FACT-605
facter ignores RFC 4193 ULAs when creating interface-specific ipaddress6 facts
Facter will use RFC 4193 addresses when creating the ipaddress6 fact, but ignores them when it tries to create interface-specific ipaddress6_$\{interface\} facts. It looks like in the latter case it is treating them the same as link-local addresses. Since these are usable, routable addresses within a LAN, they should be treated the same as any globall...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit
Jira (FACT-605) facter ignores RFC 4193 ULAs when creating interface-specific ipaddress6 facts
Title: Message Title Adrien Thebo updated an issue Facter / FACT-605 facter ignores RFC 4193 ULAs when creating interface-specific ipaddress6 facts Change By: Adrien Thebo Assignee: EricSorenson MatthewPounsett Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2856) Puppet should strip trailing white space in yaml file
Title: Message Title Kaitlin Carter created an issue Puppet / PUP-2856 Puppet should strip trailing white space in yaml file Issue Type: Improvement Assignee: Unassigned Created: 27/Jun/14 1:10 PM Labels: support Priority: Normal Reporter: Kaitlin Carter In yaml files if there are unquoted strings and trailing spaces, then those spaces are treated as part of the string which can cause unexpected results in puppet runs. This can impact external facts, and hiera data files. It would be helpful if trailing white space was trimmed from strings. Add Comment
Jira (PDB-378) Empty query on reports results in http 500
Title: Message Title Wyatt Alt commented on an issue Re: Empty query on reports results in http 500 This query appears to return the full collection of reports, not 500. Is this resolved? Add Comment PuppetDB / PDB-378 Empty query on reports results in http 500 /v3/reports?query= returns an HTTP 500 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-378) Empty query on reports results in http 500
Title: Message Title Daniele Sluijters commented on an issue Re: Empty query on reports results in http 500 Yup, I think 1.6.0 actually fixed this, just forgot to link and close the bug. Add Comment PuppetDB / PDB-378 Empty query on reports results in http 500 /v3/reports?query= returns an HTTP 500 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2691) Real-world module skeletons still use the 'description' metadata property
Title: Message Title Charlie Sharpsteen assigned an issue to Charlie Sharpsteen Puppet / PUP-2691 Real-world module skeletons still use the 'description' metadata property Change By: Charlie Sharpsteen Assignee: CharlieSharpsteen Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-605) facter ignores RFC 4193 ULAs when creating interface-specific ipaddress6 facts
Title: Message Title
Matthew Pounsett commented on an issue
Re: facter ignores RFC 4193 ULAs when creating interface-specific ipaddress6 facts
Expected values were included in the original report. PE 3 and the FreeBSD hosts both use Ruby 1.9
Add Comment
Facter / FACT-605
facter ignores RFC 4193 ULAs when creating interface-specific ipaddress6 facts
Facter will use RFC 4193 addresses when creating the ipaddress6 fact, but ignores them when it tries to create interface-specific ipaddress6_$\{interface\} facts. It looks like in the latter case it is treating them the same as link-local addresses. Since these are usable, routable addresses within a LAN, they should be treated the same as any globall...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit
Jira (FACT-605) facter ignores RFC 4193 ULAs when creating interface-specific ipaddress6 facts
Title: Message Title Matthew Pounsett updated an issue Facter / FACT-605 facter ignores RFC 4193 ULAs when creating interface-specific ipaddress6 facts Change By: Matthew Pounsett Assignee: MatthewPounsett AdrienThebo Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2654) label provider for class/define should capitalize all segments
Title: Message Title
Andy Parker commented on an issue
Re: label provider for class/define should capitalize all segments
Merged into master in 721fe6
Add Comment
Puppet / PUP-2654
label provider for class/define should capitalize all segments
When the label provider produces a label for a define/class etc. all segments of the name should be capitalized. The label is shown in error messages. Reproduce with: {code} notice Type[Foo::Bar::Fee] {code} Which displays: {code} [Type[Foo::bar::fee] {code} when it should have been {code} [Type[Foo::Bar::Fee] {code}
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1177) sshkey creates /etc/ssh/ssh_known_hosts with mode 600
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-1177 sshkey creates /etc/ssh/ssh_known_hosts with mode 600 Change By: Adrien Thebo Component/s: TypesandProviders Component/s: Community Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-480) Complete handling of undef/nil
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-480 Complete handling of undef/nil Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2732) Validation of Exec-Attribute user limits usability with non-root user.
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-2732 Validation of Exec-Attribute user limits usability with non-root user. Change By: Adrien Thebo Component/s: Community Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2737) user purge_ssh_keys cannot remove keys with spaces in the comment
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-2737 user purge_ssh_keys cannot remove keys with spaces in the comment Change By: Adrien Thebo Fix Version/s: 3.7.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2737) user purge_ssh_keys cannot remove keys with spaces in the comment
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-2737 user purge_ssh_keys cannot remove keys with spaces in the comment Change By: Adrien Thebo Component/s: Community Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2728) zypper should always be the default package provider for Suse osfamily
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-2728 zypper should always be the default package provider for Suse osfamily Change By: Adrien Thebo Fix Version/s: 4.x Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2728) zypper should always be the default package provider for Suse osfamily
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-2728 zypper should always be the default package provider for Suse osfamily Change By: Adrien Thebo Component/s: TypesandProviders Component/s: Community Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2728) zypper should always be the default package provider for Suse osfamily
Title: Message Title Adrien Thebo commented on an issue Re: zypper should always be the default package provider for Suse osfamily Matteo Cerutti for the sake of thoroughness, could you provide the release where rug was removed in favor of zypper? It'll help with bookkeeping in case we need to revisit this change. Add Comment Puppet / PUP-2728 zypper should always be the default package provider for Suse osfamily zypper package manager should always be the default package provider for Suse osfamily. Additionally, this prevents puppet agent from moaning about the presence of multiple package providers if others are also installed (e.g. Yum) along with zypper. In this case, Puppet will default to the first provider it finds, which does not happen to be the same... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-2845) Move epp() and inline_epp() to 4x function API
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2845 Move epp() and inline_epp() to 4x function API Change By: Henrik Lindberg Sprint: Week2014-6-25to2014-7-9 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2728) zypper should always be the default package provider for Suse osfamily
Title: Message Title Adrien Thebo commented on an issue Re: zypper should always be the default package provider for Suse osfamily Merged into puppet-4 in 7fc39f5. Add Comment Puppet / PUP-2728 zypper should always be the default package provider for Suse osfamily zypper package manager should always be the default package provider for Suse osfamily. Additionally, this prevents puppet agent from moaning about the presence of multiple package providers if others are also installed (e.g. Yum) along with zypper. In this case, Puppet will default to the first provider it finds, which does not happen to be the same... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2728) zypper should always be the default package provider for Suse osfamily
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-2728 zypper should always be the default package provider for Suse osfamily Change By: Adrien Thebo Fix Version/s: 4.x Fix Version/s: 4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2682) Trailing commas should be allowed in node definitions
Title: Message Title
Henrik Lindberg commented on an issue
Re: Trailing commas should be allowed in node definitions
Functional Review of this one should be obvious.
Add Comment
Puppet / PUP-2682
Trailing commas should be allowed in node definitions
Trailing commas are allowed on parametrized classes, node definitions should have the same behaviour. A comma after c should be allowed. {code} node a, b, c, { } {code}
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2532) parameter lookup produces screwy result for default values
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-2532 parameter lookup produces screwy result for default values Change By: Henrik Lindberg Assignee: HenrikLindberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-278) Variables from command line don't work as expected
Title: Message Title
Andy Parker created an issue
Hiera / HI-278
Variables from command line don't work as expected
Issue Type:
Bug
Affects Versions:
1.3.4
Assignee:
Unassigned
Created:
27/Jun/14 4:40 PM
Priority:
Normal
Reporter:
Andy Parker
This is going to be a little bit of a vague bug report. The problem is one of usability.
When hiera contains a data file with:
---
data: %{::variable}
In order to specify a value for ::variable from the command line you have to do
Works
hiera data ::variable=value
instead of, what many users might expect
Doesn't Work
hiera data variable=value
Jira (HI-278) Variables from command line don't work as expected
Title: Message Title
Andy Parker commented on an issue
Re: Variables from command line don't work as expected
A PR to make some changes to how MCollective data is used by hiera has a similar problem.
Add Comment
Hiera / HI-278
Variables from command line don't work as expected
This is going to be a little bit of a vague bug report. The problem is one of usability. When hiera contains a data file with: {noformat} --- data: %{::variable} {noformat} In order to specify a value for {{::variable}} from the command line you have to do {noformat:title=Works} hiera data ::variable=value {noformat} instead of, what man...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2532) parameter lookup produces screwy result for default values
Title: Message Title Henrik Lindberg commented on an issue Re: parameter lookup produces screwy result for default values As much as it hurts there is really no way of knowing what the resulting value of an attribute will be because the defaults are applied after all user logic has stopped being evaluated. Therefore, it is best to not even attempt to provide the default values, instead the value produced is always the value currently known to evaluation without defaults being applied. This means that lookup of the default should not be done. When it comes to virtual resources, since the attribute values here are also determined by evaluation order; a collection is scheduled for evaluation just like resources are and take place intermixed with resource evaluations, maybe it is not so crazy to allow reading their attributes. It provides a mechanism to determine how collection should be done. As with reading the attributes of a regular resource care must be taken wrt. evaluation order. What seems to be missing is the ability to check if a resource is virtual/exported and if it has been realized or not. Add Comment Puppet / PUP-2532 parameter lookup produces screwy result for default values When the future parser lookup resource parameter evaluates and there is no parameter value set by the evaluated manifest logic at that point, the evaluator then looks up the default value for that parameter. This unfortunately looks up the default value as seen from the perspective of the lookup resource parameter scope/context, and not the context...
Jira (FACT-608) Facter deliver wrong architecture to puppet
Title: Message Title Stefan Schulte moved an issue Facter / FACT-608 Facter deliver wrong architecture to puppet Change By: Stefan Schulte Component/s: Modules Affects Version/s: 3.3.2 Key: PUP FACT - 1548 608 Project: Puppet Facter Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2857) Add a Default type
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-2857 Add a Default type Issue Type: Improvement Assignee: Andy Parker Components: DSL Created: 27/Jun/14 6:01 PM Fix Versions: 3.7.0 Priority: Normal Reporter: Henrik Lindberg Currently, the _expression_ default produces a symbolic value of :default in Puppet's Ruby runtime. This value is used both as a special value in case expressions, but is also a first order value that is used in the Type api for defining upper and lower ranges of infinite value. As a consequence, these values can be used anywhere - e.g. [default] which places the value in an Array. There are really no problems with this except that the type system handles this value as an instance of Runtime[ruby, 'Symbol], which is far from ideal since it is a first order value/type in the language. In order to fix this it is best to add a specific type for this value and giving it the name Default. It should not clash with anything that exists as a resource type since default is a keyword. The only value that has this type is default, and it is an Any, but it cannot be assigned to any other type. Those that want to accept it as a parameter will need to use Default, or Variant[Default, T], it is not accepted as Data. There are
Jira (PUP-2858) remove --evaluator current switch for future parser
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-2858 remove --evaluator current switch for future parser Issue Type: Improvement Assignee: Andy Parker Components: DSL Created: 27/Jun/14 6:06 PM Fix Versions: 3.7.0 Priority: Normal Reporter: Henrik Lindberg In 3.7.0 we should remove the ability to fall back to --evaluator current as we do not want to maintain the hybrid mode (it is not how Puppet 4.0 will work), and we have not been running any tests as more and more has shifted over to the new evaluator. Removing the switch also means much of the hybrid code can be removed. Add Comment
Jira (PUP-2859) specify call by name / call by position
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2859 specify call by name / call by position Change By: Henrik Lindberg Wenowhavetwodistinctwaysofcalling;functionsandlambdasusecallbyposition,andinstantiationofclassesanddefinesusecallbyname.TheEPPfunctionspassargumentstotemplatesviacallbyname.Thespecificationshoulddocumentthisinoneplace(ratherthanrepeattherules). Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2859) specify call by name / call by position
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-2859 specify call by name / call by position Issue Type: Task Assignee: Andy Parker Components: DSL Created: 27/Jun/14 6:09 PM Fix Versions: 3.7.0 Priority: Normal Reporter: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2859) specify call by name / call by position
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2859 specify call by name / call by position Change By: Henrik Lindberg Wenowhavetwodistinctwaysofcalling;functionsandlambdasusecallbyposition,andinstantiationofclassesanddefinesusecallbyname.TheEPPfunctionspassargumentstotemplatesviacallbyname.The specification PuppetLanguageSpecification shoulddocumentthisinoneplace(ratherthanrepeattherules). Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2860) Optimize startup of puppet apply (future parser)
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-2860 Optimize startup of puppet apply (future parser) Issue Type: Improvement Assignee: Andy Parker Components: DSL Created: 27/Jun/14 6:18 PM Fix Versions: 3.7.0 Priority: Normal Reporter: Henrik Lindberg The puppet apply command is very often used as a development tool testing small snippets of puppet as well as larger scenarios. Users may thus the command over and over again. Any delays are very irritating (the smaller the snippet being tested, the more irritation). This creates an impression of Puppet's speed when used in production. (which is false, since in production it is actually throughout and overall consumption of resources to achieve that throughout that matters, not startup time). When the future parser part of the logic starts up, it creates three ecore meta models (the main AST model, the type model, and the injection model). Creating these models takes significant time when a snippet of puppet is being evaluated. These models can be serialized and cached on the first run (since they only change if the ruby logic changes). This has already been tried with the main AST model with good result. Later, we can invest more time to also get rid of the initial dynamic
