date:20140414

Jira (PUP-2246) Package provider not detected correctly on FreeBSD 10.0

2014-04-14 Thread Jeff Palmer (JIRA)

Title: Message Title










 

 Jeff Palmer commented on an issue











 






  Re: Package provider not detected correctly on FreeBSD 10.0 










This is likely a duplicate of PUP-1716












   

 Add Comment











 













 Puppet /  PUP-2246



  Package provider not detected correctly on FreeBSD 10.0 







 The standard package tool on FreeBSD 10.0 is "pkgng"  The binary is located at /usr/sbin/pkg   # puppet agent -t -v --debug --trace   Warning: Found multiple default providers for package: pip, gem; using pipIn FreeBSD 10.0, they no longer have "pkg_add" or "pkg_info" they've moved to using /usr/sbin/pkg for all.  















 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-2246) Package provider not detected correctly on FreeBSD 10.0

2014-04-14 Thread Jeff Palmer (JIRA)

Title: Message Title










 

 Jeff Palmer commented on an issue











 






  Re: Package provider not detected correctly on FreeBSD 10.0 










For what it's worth, I just tsted on FreeBSD 9.2, and pkg is also located in /usr/sbin/pkg (after it's installed)












   

 Add Comment











 













 Puppet /  PUP-2246



  Package provider not detected correctly on FreeBSD 10.0 







 The standard package tool on FreeBSD 10.0 is "pkgng"  The binary is located at /usr/sbin/pkg   # puppet agent -t -v --debug --trace   Warning: Found multiple default providers for package: pip, gem; using pipIn FreeBSD 10.0, they no longer have "pkg_add" or "pkg_info" they've moved to using /usr/sbin/pkg for all.  















 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-2246) Package provider not detected correctly on FreeBSD 10.0

2014-04-14 Thread Jeff Palmer (JIRA)

Title: Message Title










 

 Jeff Palmer commented on an issue











 






  Re: Package provider not detected correctly on FreeBSD 10.0 










I modified the ticket, I forgot that "ProviderPkg" was for Sun, not FreeBSD. So I removed that info.












   

 Add Comment











 













 Puppet /  PUP-2246



  Package provider not detected correctly on FreeBSD 10.0 







 The standard package tool on FreeBSD 10.0 is "pkgng"  The binary is located at /usr/sbin/pkg   # puppet agent -t -v --debug --trace   Warning: Found multiple default providers for package: pip, gem; using pipIn FreeBSD 10.0, they no longer have "pkg_add" or "pkg_info" they've moved to using /usr/sbin/pkg for all.  















 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-2246) Package provider not detected correctly on FreeBSD 10.0

2014-04-14 Thread Jeff Palmer (JIRA)

Title: Message Title










 

 Jeff Palmer updated an issue











 






 Puppet /  PUP-2246



  Package provider not detected correctly on FreeBSD 10.0 










For what it's worth, I just tsted on FreeBSD 9.2, and pkg is also located in /usr/sbin/pkg (after it's installed)










Change By:

 Jeff Palmer









 The standard package tool on FreeBSD 10.0 is "pkgng"The binary is located at /usr/sbin/pkg# puppet agent -t -v --debug --trace Debug: Puppet::Type::Package::ProviderPkg: file /usr/bin/pkg does not exist   Warning: Found multiple default providers for package: pip, gem; using pip I see that In FreeBSD 10.0,  they no longer have  " ProviderPkg pkg_add "  is looking in  or "pkg_info"   they've moved to using  /usr/ bin instead of /usr/ sbin ,  I'm not sure if it's the same package manager, though I suspect it is /pkg for all .   It seems like if the code just looks in both locations, this issue would be resolved.  












   

 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,

Jira (PUP-2246) Package provider not detected correctly on FreeBSD 10.0

2014-04-14 Thread Jeff Palmer (JIRA)

Title: Message Title










 

 Jeff Palmer commented on an issue











 






  Re: Package provider not detected correctly on FreeBSD 10.0 










For what it's worth, I just tsted on FreeBSD 9.2, and pkg is also located in /usr/sbin/pkg (after it's installed)












   

 Add Comment











 













 Puppet /  PUP-2246



  Package provider not detected correctly on FreeBSD 10.0 







 The standard package tool on FreeBSD 10.0 is "pkgng"  The binary is located at /usr/sbin/pkg   # puppet agent -t -v --debug --trace  Debug: Puppet::Type::Package::ProviderPkg: file /usr/bin/pkg does not existWarning: Found multiple default providers for package: pip, gem; using pipI see that "ProviderPkg" is looking in /usr/bin instead of...















 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-2246) Package provider not detected correctly on FreeBSD 10.0

2014-04-14 Thread Jeff Palmer (JIRA)

Title: Message Title










 

 Jeff Palmer created an issue











 






 Puppet /  PUP-2246



  Package provider not detected correctly on FreeBSD 10.0 










Issue Type:

  Improvement




Affects Versions:


 3.4.3




Assignee:

 Kylo Ginsberg




Components:


 Types and Providers




Created:


 14/Apr/14 8:29 PM




Environment:




uname -a FreeBSD fbsd10-64.palmerit.net 10.0-RELEASE-p1 FreeBSD 10.0-RELEASE-p1 #0: Tue Apr 8 06:45:06 UTC 2014 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64


root@fbsd10-64:/usr/local/etc/puppet # facter facterversion puppetversion facterversion => 1.7.5 puppetversion => 3.4.3




Labels:


 freebsd package




Priority:

  Normal




Reporter:

 Jeff Palmer

Jira (PUP-1547) PR (2311) Undefined method `groups' for nil:NilClass

2014-04-14 Thread Tony Vu (JIRA)

Title: Message Title










 

 Tony Vu commented on an issue











 






  Re: PR (2311) Undefined method `groups' for nil:NilClass 










Verified spec_tests passed for 


bundle exec rspec spec/unit/property/list_spec.rb














   

 Add Comment











 













 Puppet /  PUP-1547



  PR (2311) Undefined method `groups' for nil:NilClass 







 Lost quite some time in a rspec-puppet issue due to this error  Ultimately it was due to being on os x and setting {{operatingsystem}} fact to centos, making puppet unable to find providers for the user type.   {code}   NoMethodError:     undefined method `groups' for nil:NilClass   # /Users/csanchez/.rvm/gems/ruby-1.9.3-p484/gems/puppet-3.4















 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 g

Jira (PUP-2176) 4x function API for puppet function should require namespaced functions

2014-04-14 Thread Andy Parker (JIRA)

Title: Message Title










 

 Andy Parker commented on an issue











 






  Re: 4x function API for puppet function should require namespaced functions 










Merged into master in d6fd1c












   

 Add Comment











 













 Puppet /  PUP-2176



  4x function API for puppet function should require namespaced functions 







 The ability to write functions in the Puppet Programming Language is a new feature slated for Puppet 3.6.0. The current implementation allows such functions to be placed in the global name space. This support also means that functions placed under  {code}  /functions  {code}  are considered global, and functions in the module's name space must...















 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-2245) Improve ability to specify parameters in new function api

2014-04-14 Thread Andy Parker (JIRA)

Title: Message Title










 

 Andy Parker created an issue











 






 Puppet /  PUP-2245



  Improve ability to specify parameters in new function api 










Issue Type:

  Improvement




Assignee:


 Unassigned




Created:


 14/Apr/14 5:41 PM




Priority:

  Normal




Reporter:

 Andy Parker










Right now the interface for the new function api to specify parameters is (for example):



param Integer, 'a'
param Integer, 'b'
arg_count 1, 2



The param calls are fairly obvious, but the arg_count is hard to understand. We should extend the functionality of param to be able to express "required", "optional", and "last-captures-rest" kinds of parameters.












   

 Add Comment

Jira (PUP-1125) Exec checks should be turned into metaparameters

2014-04-14 Thread Charlie Sharpsteen (JIRA)

Title: Message Title










 

 Charlie Sharpsteen updated an issue











 






 Puppet /  PUP-1125



  Exec checks should be turned into metaparameters 










Change By:

 Charlie Sharpsteen




Component/s:

 Catalog Application












   

 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-1294) The 'forcelocal' parameter for the 'user' resource still performs NSS lookups for certain subkeys

2014-04-14 Thread joe b (JIRA)

Title: Message Title










 

 joe b commented on an issue











 






  Re: The 'forcelocal' parameter for the 'user' resource still performs NSS lookups for certain subkeys 










with both server and client version 3.4.3-1.el6, it appears that the usergroups are still somehow duplicating data on the initial resolution and attempting to correct to what is specified in the manifest. this user and all groups listed have forcelocal set to true. while this does not error, it skews the impression of "running smoothly" because this change is made on every puppet run.
Notice: /Stage[main]/service-server/User[service-nonis]/groups: groups changed 'dba,oinstall,oper,oinstall,oper' to 'dba,oinstall,oper'












   

 Add Comment











 













 Puppet /  PUP-1294



  The 'forcelocal' parameter for the 'user' resource still performs NSS lookups for certain subkeys 







 I have a particular configuration where a custom NSS plugin intercepts getent passwd calls and replaces the login shell with a new shell. In this situation, using the standard 'user' resource causes a false-positive for Puppet where it thinks the shell is configured as this new value, but it should be set to the value specified in the manifest. Unfortunat...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)

Jira (PUP-1106) Resource refreshes don't check for failed dependencies

2014-04-14 Thread Charlie Sharpsteen (JIRA)

Title: Message Title










 

 Charlie Sharpsteen updated an issue











 






 Puppet /  PUP-1106



  Resource refreshes don't check for failed dependencies 










This is one of the more long-standing issues with Puppet and there is a lot of history that lead to things being the way they are. The way things currently work can be summarized as:
When responding to refresh events, resources do not check the failure state of their dependencies. This is because the skip? check (which checks for failed dependencies, among other things) only affects resource syncing. Resource refreshes occur outside of of the block guarded by skip?.
The following examples demonstrate that the receipt of an event is the only thing that controls resource refreshes:



exec{'/bin/false':}
exec{'/bin/true':}

exec{'with_failed_requirement':
  command => '/bin/echo "This should not happen as the required /bin/false failed."',
  logoutput => true,
  refreshonly => true,
  require => Exec['/bin/false'],
  subscribe => Exec['/bin/true'],
}

# This should also fail as subscribe implies require.
exec{'with_failed_subscription':
  command => '/bin/echo "This should not happen as the subscribed /bin/false failed."',
  logoutput => true,
  refreshonly => true,
  subscribe => [ Exec['/bin/true'], Exec['/bin/false'] ],
}



Linking to PUP-2242, hopefully we can bring some closure to this in 4.x.










Change By:

 Charlie Sharpsteen




Summary:

 Require and Subscribe on the same refreshonly exec doesnt work Resource refreshes don't check for failed dependencies












   

 Add Comment

Jira (PUP-1106) Resource refreshes don't check for failed dependencies

2014-04-14 Thread Charlie Sharpsteen (JIRA)

Title: Message Title










 

 Charlie Sharpsteen updated an issue











 






 Puppet /  PUP-1106



  Resource refreshes don't check for failed dependencies 










Change By:

 Charlie Sharpsteen




Assignee:

 Charlie Sharpsteen












   

 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-1106) Require and Subscribe on the same refreshonly exec doesnt work

2014-04-14 Thread Charlie Sharpsteen (JIRA)

Title: Message Title










 

 Charlie Sharpsteen assigned an issue to Charlie Sharpsteen











 






 Puppet /  PUP-1106



  Require and Subscribe on the same refreshonly exec doesnt work 










Change By:

 Charlie Sharpsteen




Assignee:

 Charlie Sharpsteen












   

 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-533) PR (900): Add subqueries to events query endpoint - dalen

2014-04-14 Thread Kenneth Barber (JIRA)

Title: Message Title










 

 Kenneth Barber assigned an issue to Kenneth Barber











 






 PuppetDB /  PDB-533



  PR (900): Add subqueries to events query endpoint - dalen 










Change By:

 Kenneth Barber




Assignee:

 Kenneth Barber












   

 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-556) Analyze legacy storeconfigs export output for environments compatibility

2014-04-14 Thread Ryan Senior (JIRA)

Title: Message Title










 

 Ryan Senior assigned an issue to Ryan Senior











 






 PuppetDB /  PDB-556



  Analyze legacy storeconfigs export output for environments compatibility 










Change By:

 Ryan Senior




Assignee:

 Ryan Senior












   

 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-518) export resources fails to export array parameters

2014-04-14 Thread Ryan Senior (JIRA)

Title: Message Title










 

 Ryan Senior assigned an issue to Ryan Senior











 






 PuppetDB /  PDB-518



  export resources fails to export array parameters 










Change By:

 Ryan Senior




Assignee:

 Ryan Senior












   

 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-566) PR (125): Ensure db and db users created before validation - rickerc

2014-04-14 Thread gepetto-bot (JIRA)

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (125): Ensure db and db users created before validation - rickerc 










kbarber commented:
@rickerc ping












   

 Add Comment











 













 PuppetDB /  PDB-566



  PR (125): Ensure db and db users created before validation - rickerc 







 h2. Ensure db and db users created before validation   * Author: Chris Ricker <>  * Company:   * Github ID: [rickerc|https://github.com/rickerc]  * [Pull Request 125 Discussion|https://github.com/puppetlabs/puppetlabs-puppetdb/pull/125]  * [Pull Request 125 File Diff|https://github.com/puppetlabs/puppetlabs-puppetdb/pull/125/files]  h2. Pull Request Descr...















 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-2027) Add support for Lambda in Function Call API

2014-04-14 Thread Andy Parker (JIRA)

Title: Message Title










 

 Andy Parker assigned an issue to Andy Parker











 






 Puppet /  PUP-2027



  Add support for Lambda in Function Call API 










Change By:

 Andy Parker




Assignee:

 Andy Parker












   

 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-2244) parse error on class parameters named default

2014-04-14 Thread Joshua Hoblitt (JIRA)

Title: Message Title










 

 Joshua Hoblitt created an issue











 






 Puppet /  PUP-2244



  parse error on class parameters named default 










Issue Type:

  Bug




Affects Versions:


 2.7.25




Assignee:

 Andy Parker




Components:


 DSL




Created:


 14/Apr/14 2:56 PM




Priority:

  Normal




Reporter:

 Joshua Hoblitt










It seems that under 2.7.x (or at least 2.7.25) it is valid to define a class in the DSL with a parameter named default but it is invalid to declare a class with a parameter of the same name. Eg.
$ be puppet --version 2.7.25 $ be puppet apply -e 'class foo($default = "foo") { notify{$default:} } class  {foo:}
' notice: foo notice: /Stage[main]/Foo/Notify[foo]/message: defined 'message' as 'foo' notice: Finished catalog run in 0.04 seconds $ be puppet apply -e 'class foo($default = "foo") { notify{$default:} } class  { foo: 'default' => "baz"}
' Could not parse for environment production: Syntax error at 'default'; expected '}' at line 1 on node leo.tuc.noao.edu
Note that be == bundle exec

Jira (PDB-521) Use /dev/urandom instead of /dev/random

2014-04-14 Thread Kenneth Barber (JIRA)

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-521



  Use /dev/urandom instead of /dev/random 










Change By:

 Kenneth Barber




Sprint:

 20140409 to 20140423












   

 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-579) Work around support for legacy store configs before non-environment wire format support is dropped

2014-04-14 Thread Ryan Senior (JIRA)

Title: Message Title










 

 Ryan Senior created an issue











 






 PuppetDB /  PDB-579



  Work around support for legacy store configs before non-environment wire format support is dropped 










Issue Type:

  Bug




Assignee:


 Unassigned




Created:


 14/Apr/14 2:56 PM




Priority:

  Normal




Reporter:

 Ryan Senior










With the latest revision of the wire formats, facts, reports and catalogs now require environment information. The legacy store config migration tool doesn't know about environments because that data wasn't store in the legacy system. for PDB-556, I verified that the old format worked using the older wire format, but if we retire the older wire formats (thus requiring environments) this will cause problems. We will need to work around it by defaulting the environment, or relaxing the validation for environments.












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1

Jira (PDB-521) Use /dev/urandom instead of /dev/random

2014-04-14 Thread Kenneth Barber (JIRA)

Title: Message Title










 

 Kenneth Barber commented on an issue











 






  Re: Use /dev/urandom instead of /dev/random 










PR raised by Daniele Sluijters here: https://github.com/puppetlabs/puppetdb/pull/917












   

 Add Comment











 













 PuppetDB /  PDB-521



  Use /dev/urandom instead of /dev/random 







 We should switch PuppetDB to use {{/dev/urandom}} instead of {{/dev/random}} This will improve startup times and will help a lot of people running PuppetDB on virtual hardware as it will no longer block while waiting on enough entropy.   People are usually scared of {{/dev/urandom}} but there's no need for that in this case. {{urandom}} is perfectly well...















 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-2176) 4x function API for puppet function should require namespaced functions

2014-04-14 Thread Andy Parker (JIRA)

Title: Message Title










 

 Andy Parker assigned an issue to Andy Parker











 






 Puppet /  PUP-2176



  4x function API for puppet function should require namespaced functions 










Change By:

 Andy Parker




Assignee:

 Andy Parker












   

 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-2080) Support functions written in pp

2014-04-14 Thread Kurt Wall (JIRA)

Title: Message Title










 

 Kurt Wall assigned an issue to Kurt Wall











 






 Puppet /  PUP-2080



  Support functions written in pp 










Change By:

 Kurt Wall




Assignee:

 Kurt Wall












   

 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-2243) Using a prefix of a setting on the CLI doesn't work nor fail

2014-04-14 Thread Andy Parker (JIRA)

Title: Message Title










 

 Andy Parker updated an issue











 






 Puppet /  PUP-2243



  Using a prefix of a setting on the CLI doesn't work nor fail 










Change By:

 Andy Parker




Story Points:

 1












   

 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-2243) Using a prefix of a setting on the CLI doesn't work nor fail

2014-04-14 Thread Andy Parker (JIRA)

Title: Message Title










 

 Andy Parker updated an issue











 






 Puppet /  PUP-2243



  Using a prefix of a setting on the CLI doesn't work nor fail 










Change By:

 Andy Parker




Sprint:

 Week 2014-4-16 to 2014-4-23












   

 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-2243) Using a prefix of a setting on the CLI doesn't work nor fail

2014-04-14 Thread Andy Parker (JIRA)

Title: Message Title










 

 Andy Parker commented on an issue











 






  Re: Using a prefix of a setting on the CLI doesn't work nor fail 










The preferred solution to this would be to have partial setting names result in an error. This is to stop any new setting from squatting on a huge number of names that then can't be reliably used by applications.












   

 Add Comment











 













 Puppet /  PUP-2243



  Using a prefix of a setting on the CLI doesn't work nor fail 







 I tried this out on 3.4.3, but I'm pretty certain that it goes back much further.   The problem is that on the command line you can specify a prefix of a setting (such as {{order}} instead of {{ordering}}), but if that is done the setting does not get set. It also does not raise an error (follow tests done on a development branch).   {code:title=Settin...















 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.

Jira (PUP-2243) Using a prefix of a setting on the CLI doesn't work nor fail

2014-04-14 Thread Andy Parker (JIRA)

Title: Message Title










 

 Andy Parker created an issue











 






 Puppet /  PUP-2243



  Using a prefix of a setting on the CLI doesn't work nor fail 










Issue Type:

  Bug




Affects Versions:


 3.4.3




Assignee:


 Unassigned




Created:


 14/Apr/14 2:28 PM




Priority:

  Normal




Reporter:

 Andy Parker










I tried this out on 3.4.3, but I'm pretty certain that it goes back much further. 
The problem is that on the command line you can specify a prefix of a setting (such as order instead of ordering), but if that is done the setting does not get set. It also does not raise an error (follow tests done on a development branch).


Setting taking effect



> be puppet apply -e 'notice($::settings::certname)' --certname foo
Warning: Could not retrieve fact fqdn
Notice: Scope(Class[main]): foo
Notice: Compiled catalog for foo in environment production in 0.43 seconds
Notice: Finished catalog run in 0.04 seconds





Setting prefix used. Does not take effect also does not error



> be puppet apply -e 'notice($::settings::certname)' --certna foo
Warning: Could not retrieve fact fqdn
Notice: Scope

Jira (PUP-2150) yumrepo removable URL properties cannot be set to 'absent' in Puppet 3.5.0.

2014-04-14 Thread Kurt Wall (JIRA)

Title: Message Title










 

 Kurt Wall commented on an issue











 






  Re: yumrepo removable URL properties cannot be set to 'absent' in Puppet 3.5.0. 










Note that the "none" attribute generates an error although man 5 yum.conf says it is a legal value for the proxy attribute:



# man 5 yum.conf
[...]
**proxy** URL to the proxy server for this repository. Set to ’_none_’ to disable the global proxy
setting for this repository. If this is unset it inherits it from the global setting
[...]

# puppet apply -e "yumrepo { 'test350bug': proxy => '_none_' }"
Notice: Compiled catalog for centos6-master.localdomain in environment production in 0.06 seconds
Error: Parameter proxy failed on Yumrepo[test350bug]: Validate method failed for class proxy: Must be a valid URL at line 1
Wrapped exception:
Validate method failed for class proxy: Must be a valid URL















   

 Add Comment











 













 Puppet /  PUP-2150



  yumrepo removable URL properties cannot be set to 'absent' in Puppet 3.5.0. 







 I am on CentOS 6.5 using open-source Puppet 3.5.0. We were previously using Puppet 3.4.3.   We are using the epel module from the forge, which specifies a value of 'absent' for all of the yumrepos it manages by default. This does not work in Puppet 3.5.0, causing this error:   {noformat}  Error: Parameter proxy failed on Yumrepo[epel-testing]: Must be a...















 This message was sent by Atlassian

Jira (PDB-526) Add cleanup of unused environments

2014-04-14 Thread Kenneth Barber (JIRA)

Title: Message Title










 

 Kenneth Barber commented on an issue











 






  Re: Add cleanup of unused environments 










PR is here: https://github.com/puppetlabs/puppetdb/pull/919












   

 Add Comment











 













 PuppetDB /  PDB-526



  Add cleanup of unused environments 







 There's not currently anything to cleanup the environments table if one of the persisted environments is no longer in use. This can probably just be added to one of our existing background processes to check for unused environments and delete them.















 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-772) PR (2082): Add install options to apt

2014-04-14 Thread Kurt Wall (JIRA)

Title: Message Title










 

 Kurt Wall commented on an issue











 






  Re: PR (2082): Add install options to apt 










Peter Huene +1












   

 Add Comment











 













 Puppet /  PUP-772



  PR (2082): Add install options to apt 







 h2. Add install options apt   * Author: Matthew Barr   * Company: Kensho Technologies  * Github ID: [matthewbarr|https://github.com/matthewbarr]  * [Pull Request 2082 Discussion|https://github.com/puppetlabs/puppet/pull/2082]  * [Pull Request 2082 File Diff|https://github.com/puppetlabs/puppet/pull/2082/files]  h2. Pull Request Descriptio...















 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-1963) Generated resources never receive dependency edges

2014-04-14 Thread Charlie Sharpsteen (JIRA)

Title: Message Title










 

 Charlie Sharpsteen updated an issue











 






 Puppet /  PUP-1963



  Generated resources never receive dependency edges 










Change By:

 Charlie Sharpsteen




Summary:

 Resources type and metaparameters don't seem to work, specifically notify. Generated resources never receive dependency edges












   

 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-1433) Deprecate 'implicit' environment settings and update packaging

2014-04-14 Thread Kurt Wall (JIRA)

Title: Message Title










 

 Kurt Wall commented on an issue











 






  Re: Deprecate 'implicit' environment settings and update packaging 










That's cool. I don't mind a sanity check.












   

 Add Comment











 













 Puppet /  PUP-1433



  Deprecate 'implicit' environment settings and update packaging 







 With the new dynamic environments support, we are no longer going to support an "implicit" environment where the modulepath, manifest and config_version location is set explicitly in Puppet's configuration. Instead, packaging should ensure that the environments directory is populated with a default environment with a site.pp.   The manifestdir setting wi...















 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-1547) PR (2311) Undefined method `groups' for nil:NilClass

2014-04-14 Thread Tony Vu (JIRA)

Title: Message Title










 

 Tony Vu assigned an issue to Tony Vu











 






 Puppet /  PUP-1547



  PR (2311) Undefined method `groups' for nil:NilClass 










Change By:

 Tony Vu




Assignee:

 Tony Vu












   

 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-1964) Using undefined variable as class parameter default fails in future evaluator

2014-04-14 Thread Kurt Wall (JIRA)

Title: Message Title










 

 Kurt Wall assigned an issue to Kurt Wall











 






 Puppet /  PUP-1964



  Using undefined variable as class parameter default fails in future evaluator 










Change By:

 Kurt Wall




Assignee:

 Kurt Wall












   

 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-2242) Improve transaction event handling and propagation

2014-04-14 Thread Charlie Sharpsteen (JIRA)

Title: Message Title










 

 Charlie Sharpsteen created an issue











 






 Puppet /  PUP-2242



  Improve transaction event handling and propagation 










Issue Type:

  Epic




Assignee:

 Kylo Ginsberg




Components:


 Catalog Application




Created:


 14/Apr/14 11:44 AM




Priority:

  Normal




Reporter:

 Charlie Sharpsteen










This is an umbrella bug for issues related to the generation, propagation and handling of events in the agent transaction.












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)

Jira (PUP-2242) Improve transaction event handling and propagation

2014-04-14 Thread Charlie Sharpsteen (JIRA)

Title: Message Title










 

 Charlie Sharpsteen assigned an issue to Charlie Sharpsteen











 






 Puppet /  PUP-2242



  Improve transaction event handling and propagation 










Change By:

 Charlie Sharpsteen




Assignee:

 Kylo Ginsberg Charlie Sharpsteen












   

 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-772) PR (2082): Add install options to apt

2014-04-14 Thread Kurt Wall (JIRA)

Title: Message Title










 

 Kurt Wall assigned an issue to Kurt Wall











 






 Puppet /  PUP-772



  PR (2082): Add install options to apt 










Change By:

 Kurt Wall




Assignee:

 Kurt Wall












   

 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-2158) Directory Environments breaks many classic Config File Environments

2014-04-14 Thread Kurt Wall (JIRA)

Title: Message Title










 

 Kurt Wall updated an issue











 






 Puppet /  PUP-2158



  Directory Environments breaks many classic Config File Environments 










Change By:

 Kurt Wall




Assignee:

 Kurt Wall












   

 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-1960) realizing an empty array of resources fails in future evaluator

2014-04-14 Thread Kurt Wall (JIRA)

Title: Message Title










 

 Kurt Wall assigned an issue to Kurt Wall











 






 Puppet /  PUP-1960



  realizing an empty array of resources fails in future evaluator 










Change By:

 Kurt Wall




Assignee:

 Tony Vu Kurt Wall












   

 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-1433) Deprecate 'implicit' environment settings and update packaging

2014-04-14 Thread Joshua Partlow (JIRA)

Title: Message Title










 

 Joshua Partlow commented on an issue











 






  Re: Deprecate 'implicit' environment settings and update packaging 










Oh, right, we have the 3.5.1-rc1 version number in master now, sorry.












   

 Add Comment











 













 Puppet /  PUP-1433



  Deprecate 'implicit' environment settings and update packaging 







 With the new dynamic environments support, we are no longer going to support an "implicit" environment where the modulepath, manifest and config_version location is set explicitly in Puppet's configuration. Instead, packaging should ensure that the environments directory is populated with a default environment with a site.pp.   The manifestdir setting wi...















 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-772) PR (2082): Add install options to apt

2014-04-14 Thread Peter Huene (JIRA)

Title: Message Title










 

 Peter Huene commented on an issue











 






  Re: PR (2082): Add install options to apt 










Kurt Wall Thanks for the reminder. This was merged in d659254a3d.












   

 Add Comment











 













 Puppet /  PUP-772



  PR (2082): Add install options to apt 







 h2. Add install options apt   * Author: Matthew Barr   * Company: Kensho Technologies  * Github ID: [matthewbarr|https://github.com/matthewbarr]  * [Pull Request 2082 Discussion|https://github.com/puppetlabs/puppet/pull/2082]  * [Pull Request 2082 File Diff|https://github.com/puppetlabs/puppet/pull/2082/files]  h2. Pull Request Descriptio...















 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-772) PR (2082): Add install options to apt

2014-04-14 Thread Kurt Wall (JIRA)

Title: Message Title










 

 Kurt Wall commented on an issue











 






  Re: PR (2082): Add install options to apt 










Peter Huene I think this ticket this needs a commit message?












   

 Add Comment











 













 Puppet /  PUP-772



  PR (2082): Add install options to apt 







 h2. Add install options apt   * Author: Matthew Barr   * Company: Kensho Technologies  * Github ID: [matthewbarr|https://github.com/matthewbarr]  * [Pull Request 2082 Discussion|https://github.com/puppetlabs/puppet/pull/2082]  * [Pull Request 2082 File Diff|https://github.com/puppetlabs/puppet/pull/2082/files]  h2. Pull Request Descriptio...















 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-1433) Deprecate 'implicit' environment settings and update packaging

2014-04-14 Thread Kurt Wall (JIRA)

Title: Message Title










 

 Kurt Wall commented on an issue











 






  Re: Deprecate 'implicit' environment settings and update packaging 










Verified in 3.5.1-0.1r1-231.el6 (). Joshua Partlow I was testing a master package. If I use the correct variable name, things work as expected:



# puppet.conf
#modulepath = /etc/puppet/foo/modules
#manifest   = /etc/puppet/foo/manifests
config_version = /bin/true

# puppet config print config_version
[root@centos6-master puppet]# puppet config print config_version
Warning: Setting config_version is deprecated in puppet.conf. See http://links.puppetlabs.com/env-settings-deprecations
   (at /usr/lib/ruby/site_ruby/1.8/puppet/settings.rb:1065:in `each')
/bin/true















   

 Add Comment











 













 Puppet /  PUP-1433



  Deprecate 'implicit' environment settings and update packaging 







 With the new dynamic environments support, we are no longer going to support an "implicit" environment where the modulepath, manifest and config_version location is set explicitly in Puppet's configuration. Instead, packaging should ensure that the environments directory is populated with a default environment with a site.pp.   The manifestdir setting wi...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)

Jira (PUP-1433) Deprecate 'implicit' environment settings and update packaging

2014-04-14 Thread Joshua Partlow (JIRA)

Title: Message Title










 

 Joshua Partlow commented on an issue











 






  Re: Deprecate 'implicit' environment settings and update packaging 










Kurt Wall I think you're looking at the wrong puppet version. This is a 3.6.0, so you should only see this behavior in Puppet master right now. Although you are seeing deprecations, and you list  puppet-3.5.1-0.1rc1.231.el6.noarch...are you sure that's what's installed?
Hmm, it is config_version, not config_ver, though...maybe you are testing a master package, and you just need to test config_version?












   

 Add Comment











 













 Puppet /  PUP-1433



  Deprecate 'implicit' environment settings and update packaging 







 With the new dynamic environments support, we are no longer going to support an "implicit" environment where the modulepath, manifest and config_version location is set explicitly in Puppet's configuration. Instead, packaging should ensure that the environments directory is populated with a default environment with a site.pp.   The manifestdir setting wi...















 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 B

Jira (PUP-1433) Deprecate 'implicit' environment settings and update packaging

2014-04-14 Thread Kurt Wall (JIRA)

Title: Message Title










 

 Kurt Wall commented on an issue











 






  Re: Deprecate 'implicit' environment settings and update packaging 










Failed review against this puppet.conf. Setting config_ver does in puppet.conf does not trigger a deprecation notice in puppet-3.5.1-0.1rc1.231.el6.noarch:



# puppet.conf
modulepath = /etc/puppet/foo/modules
manifest   = /etc/puppet/foot/manifests
config_ver = /bin/true

# puppet config print config_ver
Warning: Setting manifest is deprecated in puppet.conf. See http://links.puppetlabs.com/env-settings-deprecations
   (at /usr/lib/ruby/site_ruby/1.8/puppet/settings.rb:1065:in `each')
# puppet config print modulepath
Warning: Setting manifest is deprecated in puppet.conf. See http://links.puppetlabs.com/env-settings-deprecations
   (at /usr/lib/ruby/site_ruby/1.8/puppet/settings.rb:1065:in `each')
/etc/puppet/foo/modules
# puppet config print manifest
Warning: Setting manifest is deprecated in puppet.conf. See http://links.puppetlabs.com/env-settings-deprecations
   (at /usr/lib/ruby/site_ruby/1.8/puppet/settings.rb:1065:in `each')



Commenting out modulepath and manifest does not produce a deprecation notice for config_ver:



# puppet.conf
#modulepath = /etc/puppet/foo/modules
#manifest   = /etc/puppet/foot/manifests
config_ver = /bin/true

# puppet config print config_ver
nil















   

 Add Comment











 













 Puppet /  PUP-1433



  Deprecate 'implicit' environment settings and update packaging 







 With the new dynamic environments support, we are no longer going to support an "implicit" environmen

Jira (PDB-518) export resources fails to export array parameters

2014-04-14 Thread Kenneth Barber (JIRA)

Title: Message Title










 

 Kenneth Barber assigned an issue to Unassigned











 






 PuppetDB /  PDB-518



  export resources fails to export array parameters 










Change By:

 Kenneth Barber




Assignee:

 Kenneth Barber












   

 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-1960) realizing an empty array of resources fails in future evaluator

2014-04-14 Thread Tony Vu (JIRA)

Title: Message Title










 

 Tony Vu assigned an issue to Tony Vu











 






 Puppet /  PUP-1960



  realizing an empty array of resources fails in future evaluator 










Change By:

 Tony Vu




Assignee:

 Tony Vu












   

 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-2215) An existing directory environment will use config_version from an underlying legacy environment of the same name.

2014-04-14 Thread Joshua Partlow (JIRA)

Title: Message Title










 

 Joshua Partlow commented on an issue











 






  Re: An existing directory environment will use config_version from an underlying legacy environment of the same name. 










And should be fixed in 3.6.0 when we have an environment.conf that can specify config_version for a directory environment. Though we will still need to consider the case where config_version is not specified for a directory environment, but is placed in the general puppet.conf.












   

 Add Comment











 













 Puppet /  PUP-2215



  An existing directory environment will use config_version from an underlying legacy environment of the same name. 







 [~nick.fagerlund] also noticed the following excitement:   Given a puppet.conf:   {code}  environmentpath=$condir/environments  [legacy]  config_version = /usr/bin/false  {code}   And a directory $confdir/environments/legacy   then you have:   {code}  [root@ueu8qnql450gx07 ~]# puppet agent -t --environment legacy  Info: Retrieving pluginfacts  Info: ...















 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 fro

Jira (PUP-2215) An existing directory environment will use config_version from an underlying legacy environment of the same name.

2014-04-14 Thread Joshua Partlow (JIRA)

Title: Message Title










 

 Joshua Partlow updated an issue











 






 Puppet /  PUP-2215



  An existing directory environment will use config_version from an underlying legacy environment of the same name. 










Change By:

 Joshua Partlow




Fix Version/s:

 3.6.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-2213) Directory environments interacting poorly with puppet config face

2014-04-14 Thread Joshua Partlow (JIRA)

Title: Message Title










 

 Joshua Partlow updated an issue











 






 Puppet /  PUP-2213



  Directory environments interacting poorly with puppet config face 










Change By:

 Joshua Partlow




Affects Version/s:

 3.5.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-2213) Directory environments interacting poorly with puppet config face

2014-04-14 Thread Joshua Partlow (JIRA)

Title: Message Title










 

 Joshua Partlow commented on an issue











 






  Re: Directory environments interacting poorly with puppet config face 










These are all pre-existing problems with configuration in 3.5.0.












   

 Add Comment











 













 Puppet /  PUP-2213



  Directory environments interacting poorly with puppet config face 







 I need to take more time to nail down what is going on here, but [~nick.fagerlund] noticed:   1) with environmentpath set in [main],   {code}  puppet config print manifest modulepath --environment doesnotexist  manifest = no_manifest  modulepath =  {code}   is picking up the default configured environment I believe.   2) with environmentpath set in [...















 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-2177) PR (2494) Insecure shipped Cipher settings in Passenger example config

2014-04-14 Thread Kylo Ginsberg (JIRA)

Title: Message Title










 

 Kylo Ginsberg updated an issue











 






 Puppet /  PUP-2177



  PR (2494) Insecure shipped Cipher settings in Passenger example config  










Change By:

 Kylo Ginsberg




Component/s:

 Networking Services












   

 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-2190) Accessing resource metaparameters fails in future evaluator

2014-04-14 Thread JIRA

Title: Message Title










 

 Erik Dalén commented on an issue











 






  Re: Accessing resource metaparameters fails in future evaluator 










Tags should also include the names of the scopes (both class and node) it "passed through" (yes evaluation order dependant). So if I understand you correctly those will not be visible but only tags explicitly set as a parameter? How about tags set using the tag function (on a class)?
Other metaparameters like loglevel won't show the default either?












   

 Add Comment











 













 Puppet /  PUP-2190



  Accessing resource metaparameters fails in future evaluator 







 Accessing regular parameters works fine, and when accessing unknown ones you get a decent error message. But when trying to access metaparameters you get a bad internal error   {code}  notify{foo:}  notify{Notify[foo][tag]:}  {code}   Gives:   {noformat}  Error: Evaluation Error: Error while evaluating a '[]' _expression_, undefined method `value' for ni...















 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 em

Jira (PUP-2190) Accessing resource metaparameters fails in future evaluator

2014-04-14 Thread Henrik Lindberg (JIRA)

Title: Message Title










 

 Henrik Lindberg updated an issue











 






 Puppet /  PUP-2190



  Accessing resource metaparameters fails in future evaluator 










Change By:

 Henrik Lindberg




Story Points:

 1












   

 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-2190) Accessing resource metaparameters fails in future evaluator

2014-04-14 Thread Henrik Lindberg (JIRA)

Title: Message Title










 

 Henrik Lindberg updated an issue











 






 Puppet /  PUP-2190



  Accessing resource metaparameters fails in future evaluator 










Change By:

 Henrik Lindberg




Sprint:

 Week 2014-4-09 to 2014-4-16












   

 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-2190) Accessing resource metaparameters fails in future evaluator

2014-04-14 Thread Henrik Lindberg (JIRA)

Title: Message Title










 

 Henrik Lindberg updated an issue











 






 Puppet /  PUP-2190



  Accessing resource metaparameters fails in future evaluator 










Change By:

 Henrik Lindberg




Fix Version/s:

 3.6.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-2190) Accessing resource metaparameters fails in future evaluator

2014-04-14 Thread Henrik Lindberg (JIRA)

Title: Message Title










 

 Henrik Lindberg commented on an issue











 






  Re: Accessing resource metaparameters fails in future evaluator 










o_O


The Resource parameters returns true when asked if the parameter name is an attribute of the resource.


It returns nil if no value has been set by the user


Values that have defaults (like tag) does not return the default set when the parameter tag value is obtained, but the tags method returns a TagSet that includes them


The meta-esque parameters 'title' and 'type' are not recognized as attributes by resource (neither parameters, properties nor meta-parameters) The parameter value access looks up the value, and then uses the logic to obtain the defaults. Will change the logic so that undef value does not cause an exception, but will not do anything beyond that. This means that what resource reports as the value for a parameter will be used - if it has any defaults that are applied at some point those values are not included even if the meta parameter is not set. Erik Dalén, does that sound reasonable? (for tags it means that the title and type are not included in the tag parameter when asking for it, and that title, and type are not recognized.














   

 Add Comment











 













 Puppet /  PUP-2190



  Accessing resource metaparameters fails in future evaluator 







 Accessing regular parameters works fine, and when accessing unknow

Jira (HI-233) Support array merge for automatic parameter lookup

2014-04-14 Thread Angel L. Mateo (JIRA)

Title: Message Title










 

 Angel L. Mateo commented on an issue











 






  Re: Support array merge for automatic parameter lookup 










I have not explained well. I am not talking about merging the same parameter for different classes. I'll try to explain better...
This is my /etc/puppet/hiera.yaml hiera configuration file:


/etc/puppet/hiera.yaml



:hierarchy:
  - "%{::fqdn}"
  - common



In common.yaml I have:


common.yaml



...
apache::default_mods:
  - alias
  - auth_basic
  - authn_file
  - authz_default
  - 
...



in my %{::fqdn.yaml} I have:


fqdn.yaml



apache::default_mods:
  - cgi



In my site.pp I have:


site.pp



include ::apache



What I would like is that default_mods parameter automatically binded in the include sentences was [ alias, auth_basic, authn_file, authz_default, , cgi ] and not just [ cgi ] as obtained with priority lookup.












   

 Add Comment

Jira (HI-233) Support array merge for automatic parameter lookup

2014-04-14 Thread Henrik Lindberg (JIRA)

Title: Message Title










 

 Henrik Lindberg commented on an issue











 






  Re: Support array merge for automatic parameter lookup 










I am sorry, but that is just not possible - that would mean that all lookups would be merges. There is simply no way to control this except having two different keys and doing it inside hiera. (That is however also made very difficult to add due to recursive lookup being restricted to strings only).
I am sorry, I can't explain the problem better, we seem to be talking past eachother. How do you propose that the system should differentiate between the different forms of lookup? Say a parameter $x for classes 'blue', and 'green' where you want to do a deep merge for green, but not for blue?



class blue($x) { }
class green($x) { }
include blue
include green



Where does the "same behaviour than with hiera() function" come into play here? (There is nowhere to specify the additional parameters).












   

 Add Comment











 













 Hiera /  HI-233



  Support array merge for automatic parameter lookup 







 As explained at http://docs.puppetlabs.com/hiera/1/puppet.html, automatic parameter lookup only supports priority lookup.  I think it would be interesting that it supports array (and hash) merge lookups too.















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha

Jira (HI-234) Hiera should be able to include external files within the YAML/JSON hierarchy.

2014-04-14 Thread redmine.exporter (JIRA)

Title: Message Title










 

 redmine.exporter created an issue











 






 Hiera /  HI-234



  Hiera should be able to include external files within the YAML/JSON hierarchy. 










Issue Type:

  New Feature




Assignee:


 Unassigned




Created:


 14/Apr/14 4:20 AM




Labels:


 redmine




Priority:

  Normal




Reporter:

 redmine.exporter










The crux of this issue is that I would like to be able to separate my files into more logical blocks when using the YAML or JSON configurations.
For instance:
hiera.yaml  — :backends:


yaml :hierarchy:


defaults


:yaml: :datadir: /var/lib/hiera 
In /var/lib/hiera, I would like to be able to place a directory 'defaults' and have hiera load everything under that directory.
Such as:
defaults/thing1.yaml defaults/thing2.yaml
The syntax change that I would like to see for this is to append a trailing '/' to the hierarchy statement to indicate that the directory should be parsed.
Example:
 :hierarchy:

Jira (PUP-2241) Add logging functions to static loader

2014-04-14 Thread Henrik Lindberg (JIRA)

Title: Message Title










 

 Henrik Lindberg assigned an issue to Henrik Lindberg











 






 Puppet /  PUP-2241



  Add logging functions to static loader 










Change By:

 Henrik Lindberg




Assignee:

 Andy Parker Henrik Lindberg












   

 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-2241) Add logging functions to static loader

2014-04-14 Thread Henrik Lindberg (JIRA)

Title: Message Title










 

 Henrik Lindberg created an issue











 






 Puppet /  PUP-2241



  Add logging functions to static loader 










Issue Type:

  New Feature




Assignee:

 Andy Parker




Components:


 DSL




Created:


 14/Apr/14 3:25 AM




Fix Versions:


 3.6.0




Priority:

  Normal




Reporter:

 Henrik Lindberg










The new loader system's static loader should contain the logging functions (notice, warn, etc.)












   

 Add Comment

Jira (PUP-2240) support unfold/splat of array

2014-04-14 Thread Henrik Lindberg (JIRA)

Title: Message Title










 

 Henrik Lindberg assigned an issue to Henrik Lindberg











 






 Puppet /  PUP-2240



  support unfold/splat of array 










Change By:

 Henrik Lindberg




Assignee:

 Andy Parker Henrik Lindberg












   

 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-2240) support unfold/splat of array

2014-04-14 Thread Henrik Lindberg (JIRA)

Title: Message Title










 

 Henrik Lindberg created an issue











 






 Puppet /  PUP-2240



  support unfold/splat of array 










Issue Type:

  New Feature




Assignee:

 Andy Parker




Components:


 DSL




Created:


 14/Apr/14 3:17 AM




Fix Versions:


 3.6.0




Priority:

  Normal




Reporter:

 Henrik Lindberg










Support unfold/splat operator that unfolds an array/hash as individual arguments.



*value



When splat operator is applied to a hash, the hash is transformed into an array of [key, value] tuples. An array is verbatim. All other values are wrapped in an array.
When a Splat operation appears in an argument list (function call), and in a literal list, the array of values produced by splat are unfolded.



sprintf(*["%d", 10])  # same as sprintf("%d", 10)
[1,*[2,3],4]  # same as [1,2,3,4]



Without this, users have to do manual unfolding (i.e. $a[0], $a[1], etc), and must know the size of what is being unfolded.

Jira (PUP-2239) logical operations in ?{}

2014-04-14 Thread Faye Gibbins (JIRA)

Title: Message Title










 

 Faye Gibbins updated an issue











 






 Puppet /  PUP-2239



  logical operations in ?{} 










Change By:

 Faye Gibbins









 Given two booleans: $bool1 and $bool2 it would be nice to do:($bool or $bool2)?{true=> ..., false => ...}ATM this produces  and  an  error in the puppet parser. The work around is a clumsy hack, viz:foo::bar {'some property': value => $bool1?{true => $bool2?{true=>.,false => .}false => $bool2?{..},},}












   

 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-2239) logical operations in ?{}

2014-04-14 Thread Faye Gibbins (JIRA)

Title: Message Title










 

 Faye Gibbins created an issue











 






 Puppet /  PUP-2239



  logical operations in ?{} 










Issue Type:

  Improvement




Affects Versions:


 3.4.3




Assignee:


 Unassigned




Created:


 14/Apr/14 1:44 AM




Environment:


scientific linux 6.5




Labels:


 conditionals




Priority:

  Normal




Reporter:

 Faye Gibbins










Given two booleans: $bool1 and $bool2 it would be nice to do:
($bool or $bool2)? {true=> ..., false => ...}
ATM this produces and error in the puppet parser. The work around is a clumsy hack, viz:
foo::bar {'some property': value => $bool1?{ true => $bool2? {true=>.,false => .}
 false => $bool2? {..}
, }, }

68 matches

Mail list logo