Title: Message Title
Gabriele Paggi commented on PUP-1515
Re: Invalid parameter provider for custom types/providers
So, to summarize: when the Puppet master loads a Type, it searches the environment that the agent requested. When it loads providers for that type, it searches the default environment instead of the one the agent requested.
Charlie Sharpsteen, what is the name of the default environment? Is it production? I'm seeing the same issue with only one environment named prd. The workaround I'm using is to define a production environment pointing to the same directories as the prd one:
# Always create production pointing to the first defined environment
# to circumvent PUP-1515 (pluginsync, custom provider/type)
[production]
manifest = /etc/puppet/environments/prd/manifests/
modulepath = /etc/puppet/environments/prd/.
[prd]
manifest = /etc/puppet/environments/prd/manifests/
modulepath = /etc/puppet/environments/prd/..