Jira (PUP-1806) Varargs support for the new function API

2014-03-23 Thread Henrik Lindberg (JIRA)
Title: Message Title










 

 Henrik Lindberg commented on an issue











 






  Re: Varargs support for the new function API 










This is now implemented as part of the first cut of the API in PUP-1799. Suggest we keep this ticket until we are happy with how it works. Otherwise repurpose this ticket to what remains to be fixed.












   

 Add Comment











 













 Puppet /  PUP-1806



  Varargs support for the new function API 







 There needs to be some way of specify varargs in the new function API, but in a way that still lets us do some type checking of the arguments.















 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-1799) New Function API

2014-03-23 Thread Henrik Lindberg (JIRA)
Title: Message Title










 

 Henrik Lindberg commented on an issue











 






  Re: New Function API 










pre-docs to follow 2/3 ds done (there is a bit of documentation in the Puppet::Functions class).












   

 Add Comment











 













 Puppet /  PUP-1799



  New Function API 














 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-1072) support HTTP(S) URL as the file 'source'

2014-03-23 Thread Philip Garrett (JIRA)
Title: Message Title










 

 Philip Garrett commented on an issue











 






  Re: support HTTP(S) URL as the file 'source' 










I like to keep my puppet modules in git, but I don't want the binaries in version control. This would make that easier.












   

 Add Comment











 













 Puppet /  PUP-1072



  support HTTP(S) URL as the file 'source' 







 Lots and lots of folks want to be able to do this:   file { "/tmp/example.txt": source => 'http://example.com/example.txt' }   This would be good to support; obviously the metadata for the HTTP URI is much less available than via puppet file serving, but this would make a lot of people very, very happy.















 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-2020) Expose config_version via REST Api

2014-03-23 Thread Peter Meier (JIRA)
Title: Message Title










 

 Peter Meier created an issue











 






 Puppet /  PUP-2020



  Expose config_version via REST Api 










Issue Type:

  New Feature




Assignee:

 Andy Parker




Components:


 Networking Services




Created:


 23/Mar/14 10:36 AM




Priority:

  Normal




Reporter:

 Peter Meier










It would be interesting to expose the config_version via REST-Api, so that people having an own config_version script, would be able to query from the puppet client if the config_version changes since the last run and e.g. only run puppet apply then.












   

 Add Comment











 










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

Jira (PUP-1738) Resource provider should be able to specify suitability and weight

2014-03-23 Thread Kylo Ginsberg (JIRA)
Title: Message Title










 

 Kylo Ginsberg commented on an issue











 






  Re: Resource provider should be able to specify suitability and weight 










I didn't follow all the discussion in https://github.com/puppetlabs/puppetlabs-stdlib/pull/204, but FWIW as of 3.5.0 you can specify default providers using features (see https://github.com/puppetlabs/puppet/blob/571b4468983d604e96752d9de8798d728de43d81/lib/puppet/provider.rb#L294-L305).
E.g. this now works:



defaultfor :feature => :posix



(And yes it was an accident that it appeared to work for the one use in core puppet, sigh.)












   

 Add Comment











 













 Puppet /  PUP-1738



  Resource provider should be able to specify suitability and weight 







 Currently a resource provider have two gaps:   1. We need the ability to specify a default provider without reliance on facts (see https://github.com/puppetlabs/puppetlabs-stdlib/pull/204).  2. We need the ability to specify weight in the event multiple providers are suitable.   Similar to facter, we should support a provider's ability to specify:   {n...















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




 
   

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

2014-03-23 Thread Marius Rieder (JIRA)
Title: Message Title










 

 Marius Rieder created an issue











 






 PuppetDB /  PDB-518



  export resources fails to export array parameters 










Issue Type:

  Bug




Affects Versions:


 1.6.2




Assignee:


 Unassigned




Created:


 23/Mar/14 6:21 AM




Environment:


Ubuntu 14.04 with puppet and puppetdb from apt.puppetlabs.com




Priority:

  Normal




Reporter:

 Marius Rieder










For exported Resources with parameters which value is a Array the storeconfig export fails to collect them. Instead of collecting all the parameter values into a array it simply override the value with each value in turn. Resulting in a single value instead of a array.
I was able to fix this for our export. https://github.com/jiuka/puppetdb/commit/b0299dd89391421e47a64a04d01d052905a9880d












   

 Add Comment


Jira (PUP-2019) Expose catalog version

2014-03-23 Thread redmine.exporter (JIRA)
Title: Message Title










 

 redmine.exporter created an issue











 






 Puppet /  PUP-2019



  Expose catalog version 










Issue Type:

  New Feature




Assignee:


 Unassigned




Created:


 23/Mar/14 5:18 AM




Labels:


 redmine




Priority:

  Normal




Reporter:

 redmine.exporter










Hi,
Would it be possible to expose the catalog version so that something like the following in the puppet.conf would work?
postrun_command=/usr/local/sbin/postrun.sh $environment $catalog.version
I've tried parsing the last_run_summary.yaml file but that is only updated after postrun is executed.












   

 Add Comment