Hi Mark,
You can check if a type is available by running puppet describe -l
This will print out all available puppet custom types.
Best,
Martin
> On 11. Mar 2021, at 18:11, Mark Dixon wrote:
>
> Hi Martin,
>
> Thanks - but that doesn't seem to be the problem, as it's already in the
>
Hey Molly,
The PDK has already been ignoring the /spec directory for quite some time,
so I think this is totally appropriate. It won't even have any effect for
PDK enabled modules from the Forge. Those files are only used for
development purposes, and if you're doing that in your production
Molly,
Should this be an all or nothing or off by default with the option to include
them?
Thanks,
Steve
From: puppet-users@googlegroups.com On Behalf
Of Molly Waggett
Sent: Thursday, March 11, 2021 7:04 PM
To: puppet-users@googlegroups.com
Cc: Froyo Team
Subject: [Puppet
Hey folks!
We are planning an r10k feature to stop deploying module spec directories.
This will lower disk usage, particularly for folks with a lot of modules
and multiple compilers.
Our hope is to enable this behavior by default, but leave the option to opt
out (i.e. continue including spec
On Sat, Mar 6, 2021 at 3:18 AM Bart-Jan Vrielink
wrote:
> /etc/puppetlabs/puppetserver/ca is not a volume listed in the
> docker-compose file. Unless that directory is symlinked to somewhere under
> /etc/puppetlabs/puppet/,
> that directory would get lost whenever the container gets updated.
Hi Martin,
Thanks - but that doesn't seem to be the problem, as it's already in the
modulepath. Just noticed something odd, will prod a bit more (unfortunately
next week now).
Best,
Mark
On Thursday, March 11, 2021 at 7:04:06 AM UTC Martin Alfke wrote:
> Hi Mark,
>
> please check module
I am thinking we can make a whole module out of this issue and fix the
problem with puppet code. This problem appears in other tooling as well. I
have the following in my code now which patches the lsb-release file and
appears to make things works.
