Henrik thanks for the reply,
I probably shouldnt have posted the tree info, i am testing both the hiera
in-module as well as the
function in-module lookup thats why it looks like an environment. But I can
see data function return on the server,
#===================================
# On server
% puppet apply -e 'notice vartmp::data()'
Notice: Scope(Class[main]): {vartmp::localerb => vartmp/vartmp.erb,
vartmp::vtfile => /var/tmp/VAR-TMP-FILE}
Notice: Compiled catalog for puppetserver in environment production in 0.08
seconds
Notice: Applied catalog in 0.16 seconds
You have new mail in /var/spool/mail/root
Its the client that is not getting the data. I can put the function in the
modules namespace, but it seemed like the
documentation says you dont need to..
On Wednesday, February 24, 2016 at 11:56:38 PM UTC-5, Henrik Lindberg wrote:
>
> On 24/02/16 21:57, RG wrote:
> >
> > I am using puppet 4.3 and it looks like the new function lookup provider
> > is not working, unless i am missing something.
> > I am working from this:
> >
> https://docs.puppetlabs.com/puppet/latest/reference/lookup_quick_module.html
> >
> > I am just testing with this simple example.
> > % puppet status
> > {
> > "is_alive": true,
> > "version": "4.3.2"
> > }
> >
> > % tree
> > .
> > ├── data
> > │ └── common.yaml
> > ├── functions
> > │ └── data.pp
> > ├── hiera.yaml
> > ├── manifests
> > │ └── init.pp
> > ├── metadata.jason
> > └── templates
> > └── vartmp.erb
> > #==================================
> >
> > % cat functions/data.pp
> > function vartmp::data() {
> >
> > $base_params = {
> > 'vartmp::localerb' => 'vartmp/vartmp.erb',
> > 'vartmp::vtfile' => '/var/tmp/VAR-TMP-FILE',
> > }
> >
> > $base_params
> > }
> >
> > #==================================
> > % cat manifests/init.pp
> > # Class : vartmp
> > #
> > class vartmp (
> > $vtfile,
> > $localerb
> > ) {
> >
> > file { $vtfile:
> > owner => 'root',
> > group => 'root',
> > mode => '0644',
> > content => template($localerb),
> > }
> >
> > }
> >
> > #==================================
> > % egrep data metadata.jason
> > "data_provider": "function"
> > #==================================
> >
> This looks odd.The rest of your layout looks like it is for an
> environment. An environment does not have a metadata.json that is only
> for modules. For an environment you need to specify the data_provider in
> environment.conf and set it to 'function'. It will then call the
> function named 'environment::data()'.
>
> If you are intstead doing this for a module, the name of the function
> should be in the module's namespace e.g. 'mymodule::data()'.
>
> Does that help?
>
> Since the data functions are just regular functions you can test by
> calling them directly - e.g:
>
> puppet apply -e 'notice environment::data()'
> puppet apply -e 'notice mymodule::data()'
>
> You can also use 'puppet lookup' command line tool with '--explain' to
> get detailed trace information about what is going on.
>
> There are bugs in 4.3 though, but the basic use cases should work.
> There are many fixes in the upcoming puppet 4.4.0 for lookup/data binding.
>
>
> - henrik
>
> > puppet-lint and pupper parser validate both return clean.
> >
> > #==================================
> > On client.
> > % puppet status
> > {
> > "is_alive": true,
> > "version": "4.3.2"
> > }
> >
> > % puppet agent -t
> > Info: Using configured environment 'production'
> > Info: Retrieving pluginfacts
> > Info: Retrieving plugin
> > Info: Loading facts
> > Error: Could not retrieve catalog from remote server: Error 400 on
> > SERVER: Evaluation Error: Error while evaluating a Resource Statement,
> > Class[Vartmp]:
> > expects a value for parameter 'localerb'
> > expects a value for parameter 'vtfile' on node puppetclient
> > Warning: Not using cache on failed catalog
> > Error: Could not retrieve catalog; skipping run
> >
> > Anybody know/see what i am missing?
> > Thanks
> >
> > --
> > You received this message because you are subscribed to the Google
> > Groups "Puppet Users" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> > an email to puppet-users...@googlegroups.com <javascript:>
> > <mailto:puppet-users+unsubscr...@googlegroups.com <javascript:>>.
> > To view this discussion on the web visit
> >
> https://groups.google.com/d/msgid/puppet-users/f424077b-1656-4626-b971-033433a570e5%40googlegroups.com
>
> > <
> https://groups.google.com/d/msgid/puppet-users/f424077b-1656-4626-b971-033433a570e5%40googlegroups.com?utm_medium=email&utm_source=footer>.
>
>
> > For more options, visit https://groups.google.com/d/optout.
>
>
> --
>
> Visit my Blog "Puppet on the Edge"
> http://puppet-on-the-edge.blogspot.se/
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/8a0cbf3e-bb76-48fe-971b-c7db6c6cb17a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
