Open absld opened 2 months ago
I'm having exactly the same issue... Any clue on how to mitigate it?
(And I really mean exactly the same... also triggered by PuppetDB module)
Hello, same here ... Any news please ? Thanks.
When you deploy your environment, do you generate types? https://www.puppet.com/docs/puppet/8/environment_isolation.html
When you deploy your environment, do you generate types? https://www.puppet.com/docs/puppet/8/environment_isolation.html
yes
Hello all,
just gave that another try. After generating types like recommended by @ekohl, I was able to successfully run puppet. @flepoutre please check whether you really generate types as this solved the issue for me.
For all who also use the puppetboard module of voxpupuli: There is a issue within the puppet-python module in its current version. You need to use the latest git commit from the repository instead of the latest tag at the moment. Stumbled upon this problem after I got the puppetlabs-postgresql module working.
Describe the Bug
I'm using puppetlabs-postgresql 10.3.0 together with puppetlabs-puppetdb 8.1.0. In
database/postgresql.pp
manifest of puppetlabs-puppetdb,postgresql::server::extension
class is called:Within
postgresql::server::extension
,$instance
has a default set to 'main'. Then,postgresql_psql
type is called the following way:Unfortunately, this results in the following error:
My guess is that this fails due to quoting problems. A string containing double quotes is assigned to
$command
variable. Maybe they break the double quotes inpostgresql_psql { "${database}: ${command}":
.Expected Behavior
No mysterious error complaining about missing parameters which are acutally properly defined.
Steps to Reproduce
Steps to reproduce the behavior:
mod 'puppet-puppetboard', '9.0.0'
=>mod 'puppet-puppetboard', '10.0.0'
2.2mod 'puppetlabs-puppetdb', '7.13.0'
=>mod 'puppetlabs-puppetdb', '8.1.0'
2.3mod 'puppetlabs-postgresql', '9.0.3'
=>mod 'puppetlabs-postgresql', '10.3.0'
Environment