Is this really still true? From the looks of the stdlib source of
ensure_resource it seems like it just parses parameters and calls
create_resources .
Trying to understand if this is 3 year old lore or still valid in 2017.
Regards,
== k+ ==
On Monday, March 31, 2014 at 12:24:30 AM UTC-4, At
stall"],
}
Use this:
file { '/etc/openldap/ldap.conf':
ensure => file,
content => template('ldap/ldap.conf.erb'),
require => Class["ldap::install"],
}
See:
https://docs.puppet.com/puppet/latest/types/file.html#file-attribute-content
ken.
The SSL certificate for several of our domains has expired with the result
that attempts to access various services will throw expired/invalid
certificate errors. Notably this includes our apt and yum repositories and
other software download servers.
We are currently working the issue and replacem
Certificates for apt, yum, and downloads have been updated and those
services should be behaving normally again.
On Sun, Aug 13, 2017 at 2:34 PM, Ken Johnson wrote:
> The SSL certificate for several of our domains has expired with the result
> that attempts to access various services will
fix that? Really appreciate any help on this.
>
>
If the file changes, fooacl on its own won't notice the change and won't
reset the ACLs. You need to notify the class to ensure it does catch
this. We have something like this for ours that we put after the fooacl
resource:
File[]
ich looks like its a 2.x to me)
You should also check your puppet master logs to see if there are any
errors while submitting the catalog.
ken.
On Wed, May 18, 2016 at 7:21 AM, Harish Kothuri wrote:
> Hi,
>
> I am trying to access resources from PuppetDB API as follows, API makes a
>
ough,
its not possible anyway.
Irrespective of this imaginary world, one could store the data in
hiera to be consumed, if one chose to - or somewhere else, it matters
little for the resulting graph.
ken.
--
You received this message because you are subscribed to the Google Groups
"Puppet
ion for multiple clusters, at least then you have continuity,
people will know where to go to do look into problems etc.
ken.
On Thu, Mar 3, 2016 at 5:11 PM, Daniel Urist wrote:
> I've created a module to configure a caching nginx proxy. I am running
> several of these proxies behin
if this is off-topic for this list in any way.)
Thanks in advance.
--
Ken Lareau
--
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...@goo
en I wouldn't trust the schema
to be in a good state.
In particular, check these function indexes were created using the
proper encoding, else performance is going to be slow:
https://github.com/puppetlabs/puppetdb/blob/3.2.3/src/puppetlabs/puppetdb/scf/migrate.clj#L1492-L1507
ken.
On Wed
/puppetdb/blob/3.2.2/src/puppetlabs/puppetdb/scf/migrate.clj#L1534
So ... why not just use 3.2.3 anyway? Since it looks like the
migration has taken place, and its the latest release.
ken.
On Wed, Feb 24, 2016 at 10:40 AM, Fabrice Bacchella
wrote:
> I'm running puppetdb on ScientificLinux 6.7
s.com/browse/PUP-3463
ken.
On Mon, Feb 1, 2016 at 11:08 PM, wrote:
> Please let me know if Puppet has a feature which can send emails specific to
> an environment?
> The tagmail feature sends emails of all the agents communicating to the
> master and that is not what we want in o
information on the specifics of the
release can be found in the official release notes:
https://docs.puppetlabs.com/puppetdb/3.2/release_notes.html
Contributors
---
Andrew Roetker, Ken Barber, Nick Fagerlund, Rob Browing, Russell Mull,
Ryan Senior, Tim Skirvin, Wayne Warren and Wyatt Alt
> test.local
> Currently active
> No catalog received
> Last facts: 2015-10-27T10:40:49.778Z
>
> In the puppetdb logs I see '[replace facts]', but no '[replace catalog]'
> like mentioned in the documentation.
The first error above means the catalog does no
lding masters from scratch its
good to have control of this step anyway, since you often want to
manage the CA.
> On Friday, 9 October 2015 21:01:00 UTC+1, Ken Barber wrote:
>>
>> On Fri, Oct 9, 2015 at 4:35 AM, Dan wrote:
>> > Hi Wyatt,
>> >
>> >
On Fri, Oct 9, 2015 at 4:35 AM, Dan wrote:
> Hi Wyatt,
>
> Thanks for the pointer! I found the full stack trace which gives a better
> error:
>
> I just need to workout how to configure the SSL configuration now.
Try `puppetdb ssl-setup` on the command line. It requires that you've
done a full p
--data-urlencode
'query=["or",["=","name","kernelversion"],["=","name","operatingsystem"]]'
[ {
"certname" : "kb.local",
"environment" : "production",
"name"
minus performs its HTTP queries:
https://github.com/puppetlabs/puppetdb/blob/master/puppet/lib/puppet/indirector/resource/puppetdb.rb#L18-L35
If you use that action facility, it does all the right stuff for you,
reads the puppetdb.conf file, does failover if necessary, uses SSL.
Its not nec
your routes.yaml look like? This can be
misconfigured to always use PDB for that information, which is bad.
Facts should come from agents, not from a cache inside PDB during
compilation :-).
Also - double check your facts yaml cache, wipe it if necessary (or
back it up just in case) to en
n a fact. If you
>> want all the package data, a well structured fact is suitable for
>> this. That will then get submitted each run, and can be queried via
>> the various facts endpoints.
>>
>
> Ok, that sounds doable. I just turned up this sample code ,
> http:
ackage"], ["=","resource-title","libc6"]]'
>
> will show what's changed or failed with libc6 .
>
> can I get the current package version number through an API call?
An alternative is to have this data be collected in a fact. If you
want al
hat you want. If you get stuck further down the line,
respond to this thread.
We have plans to solidify this story, and make it closer to our core
offerings but I'm wary to get into a vapourware discussion until we
have something to show. For now, what I've provided is where you want
to l
ppet.conf:
http://docs.puppetlabs.com/puppetdb/3.0/connect_puppet_master.html#edit-puppetconf
ie. storeconfigs = false in the [master] section.
ken.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving
Hi Peter!
On Thursday, June 25, 2015 at 9:45:51 PM UTC-7, Peter Huene wrote:
>
> Hi Ken!
>
> On Thu, Jun 25, 2015 at 11:53 AM, Ken Bowley > wrote:
>
>> While testing puppet 4 to see if it was ready for production (still not),
>> I now get to deal with the new Fa
While testing puppet 4 to see if it was ready for production (still not), I
now get to deal with the new Facter 3.0.
Hopefully ruby based facter won't be totally abandoned, since the C++ based
version is going to be an annoyance on non-PL supported systems.
The first thing I noticed is that a c
le wrote:
> > On 6/22/15, 3:08 PM, "Vince Skahan" >
> wrote:
> >
> >> On Thursday, June 18, 2015 at 4:18:37 PM UTC-7, Ken Bowley wrote:
> >>> This is better than what is currently being used, but I'm strongly in
> the AIO
> >>&g
This is better than what is currently being used, but I'm strongly in the
AIO idea to be stupid. Split it into multiple packages and use proper
dependencies like every other sane packaging system has done for a long,
long time.
If all you do is bump the version of facter, then only have me dow
I managed to get it to work by editing tagmail.rb and hard coding any of
the areas where it tries to use Puppet[:*] config options that don't exist
and can not work with puppet 4.1.
On Thursday, June 11, 2015 at 1:30:52 PM UTC-7, Ken Bowley wrote:
>
> While I ignore puppet 4's b
While I ignore puppet 4's brain-dead stupid fact behaviour when using
puppetdb, I'm on to the issue of getting puppet to mail reports when
something changes on a node.
Since the built-in tagmail is no longer an option, I decided to look at the
tagmail module. As far as I can tell, the puppetla
I'm running puppet 4.1.0 in a test VM in preparation for an eventual
migration from 3.8.1. I've recently run into an issue that seems to be
mentioned in https://tickets.puppetlabs.com/browse/PDB-949
Here's a little back info; My VM is a copy of our production puppet
master, but with 4.1.0 an
e use of Puppet 4 for the one that is failing.
If you can provide the normal diagnostic info, like distro, version of
distro and exact version of all the elements (like puppetdb &
puppetdb-terminus) this might be useful.
Also - what does your /etc/puppet/puppetdb.conf file look like?
ken.
even a large one would need
30 seconds, but if you are seeing delays in starting postgresql then
it's worth a try, just seems odd for a small database, PG usually
takes less than a second to start.
ken.
--
You received this message because you are subscribed to the Google Groups
"Pupp
ated tests for yet ... and
we've got a bug we haven't noticed. At least this wouldn't surprise
me.
You definitely want to prefer PostgreSQL over embedded btw, so this is
the correct direction to follow.
Sorry about all the hassles again mate :-).
ken.
--
You received this message
>> Even using the “embedded” database is apparently useless, as puppet is still
>> not able to connect to puppetdb.
>>
>> In addition, puppetdb is very obviously not creating it’s firewall rules
>> even though I haven’t disabled that feature.
>
> This is interesting/surprising, but it sounds like t
, git or some other mechanism? I'm asking for these
details so I can try and recreate this and see what is happening. It
shouldn't bomb this hard, and I'm wary we have a bug somewhere.
Can you also send me a full debug output run for this in a gist
(gist.github.com) from start to fi
ps
some performance improvements can be made on that end of the stack.
Have you looked into why the queries are taking so long to return yet?
ken.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and s
/puppetdb/master/configure.html#report-ttl
Disk space is the main cost, however sometimes larger storage
requirements will sometimes slow down certain queries also, but YMMV.
ken.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To un
der it, but most of our efforts should be put into
5.x of the module TBH.
ken.
--
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...@goo
d]# psql -h localhost puppetdb puppetdb
> Password for user puppetdb:
> psql (9.4.1, server 9.3.6)
> Type "help" for help.
>
> puppetdb=>
>
> Regards,
>
> Dominique Arpin
ken.
--
You received this message because you are subscribed to the Google Groups
"Puppet U
r to update their package (it's still a few revisions
behind anyhow, I wouldn't advise a 2.2.0 if you can avoid it) or roll
your own SLES specific package.
ken.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsub
e node much easier, and alleviates other
noise caused by 'general load'.
Also, if you haven't done so already - the new Clojure based puppet
server will potentially give you perf gains over the passenger
mechanism, I would definitely consider experimenting with it, if you
haven'
that if you have any questions or
trouble migrating to PostgreSQL, the puppet-users mailing list and the
#puppet IRC channel are watched by a number of us in the PuppetDB team
(not to mention, by other avid community users who are also helpful),
so we can help where necessary with any problems.
Reg
ff/cache
> available
> Mem: 6649 4033459 82787
> 5984
> Swap: 1023 0 1023
>
> can anyone help ?
Anything in the logs in /var/log/pe-puppetserver that would give you a
better clue as to why its failing?
ken.
-
t will throw this message. Its not
critical, and recently we've moved this error back to being a DEBUG
(prepped for a future release). Yes, it can be safely ignored.
ken.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscr
this won't scale
very well ultimately, as you'll need to add more of these proxies for
each DC you add just to establish trust. But it would work, I guess
:-).
ken.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To
nsource edition.
The guidelines for Logo usage are here: https://puppetlabs.com/styleguide/brand
And right at the end of that document, there is a link to a document
that defines the legal terms of use for our website and its content
(and logos included): https://puppetlabs.com/terms
ken.
--
Y
also. Any ideas?
I'm not sure you need a proxy per se, it depends on your exact needs.
Either way, you still end up having to deal with certificates.
ken.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this
tuning.
There is also a small chance this is a bug with some old revision, but
I can't see that specifically, I suspect its the environment.
ken.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and
the master how to communicate with the
service, so its configuration file lives alongside the puppet/master
configuration files.
ken.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving email
een offline and have older versions of puppet that need to be
upgraded.
On Friday, April 17, 2015 at 4:25:59 PM UTC-7, Kylo Ginsberg wrote:
>
> On Fri, Apr 17, 2015 at 3:12 PM, Ken Bowley > wrote:
>
>> Puppet 4 needs a lot of new directories in order to even attempt to run.
&g
;t involve firing up a new puppet 4 server
to run alongside the puppet 3 server.
On Friday, April 17, 2015 at 3:04:51 PM UTC-7, Tim Skirvin wrote:
>
> Ken Bowley > writes:
>
> > We've been using Puppet since the 0.24 days, and it's always been fairly
> > sim
We've been using Puppet since the 0.24 days, and it's always been fairly
simple to add in a new system.
Do a base install (Linux or Mac OS X)
Install Ruby if Linux
gem install puppet
run puppet
sign the cert on the puppetmaster
let puppet take care of everything else.
This was easy, easy to docu
s.com/references/latest/type.html#yumrepo
ken.
--
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 d
nd are you using PostgreSQL (also what exact version)? How
many reports/nodes are we talking about here, and what kind of CPU/IO
effect are you seeing, that is, what statistics have you collected so
far?
ken.
--
You received this message because you are subscribed to the Google Groups
"Pu
tting caught by the
OOMkiller in Linux. I have no other information about your system then
what you've given me, so I can't make a judgement on whether 12 GB is
high or not for you. It does seem high, although I could understand
this increase in the setting if you were processing a lo
ing logged anywhere. We'll have this fixed in a future
release.
For now the recommendation is to increase your heap size until the
behaviour stabilises:
https://docs.puppetlabs.com/puppetdb/2.2/configure.html#configuring-the-java-heap-size
ken.
--
You received this message because you are
-heap-size
ken.
On Mon, Feb 16, 2015 at 11:23 AM, James Green wrote:
> We have a puppet-master box with the following installed:
>
> root@puppet-master:/var/log/puppetdb# dpkg -l | grep puppet
> ii facter 2.4.1-1puppetlabs1 all
> Ruby mod
://wiki.postgresql.org/wiki/Apt
ken.
On Mon, Feb 16, 2015 at 9:28 AM, Stefan Dietrich
wrote:
> Hi,
>
> we are currently evaluating to update our Puppet infrastructure, one
> open item is the required PostgreSQL version for PuppetDB 2.2.x.
>
> Does PuppetDB 2.2.x still support PostgreSQL 9.2?
>
&g
g == 'nagios1' |>>
See:
https://docs.puppetlabs.com/puppet/latest/reference/lang_collectors.html
ken.
--
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
i puppet-common 3.7.3-1puppetlabs1
> all Centralized configuration management
> ii puppetlabs-release 1.0-11
> all "Package to install Puppet Labs gpg key and apt repo"
Its been a while since I've hacked on facter so excuse m
fail early if we
receive a large catalog, and save the whole instance. Alternatively we
could break up the catalog into multiple pieces, but that requires a
more complicated process so is less viable.
ken.
--
You received this message because you are subscribed to the Google Groups
"Puppet U
e me a little time to set up. Before I do
this, have you tested this with Puppet 3.7.3 yet? Also, is this only
happening in 1 environment, can you reproduce this on another puppet
master perhaps?
ken.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users&qu
om
> /etc/puppet/routes.yaml: Could not find terminus puppetdb for indirection
> facts
>
> Is there something special we need to do to the config.ru or something so
> that it can find the puppetdb terminus from the gem thats installed?
That just looks like the necessary ruby library files a
on, you may find PuppetDB is being used for
facts instead of using the received facts from an agent. That is, it
might get populated the first time, but subsequent runs will only
retrieve facts from the first run from PuppetDB and only those will
appear in your manifest scope.
ken.
--
You received
atches yourself.
What's more, ActiveRecord storeconfigs has been dropped in Puppet 4
completely afaik so it is no longer even an option. Also 2.7.x is EOL
fyi, so you're working against the grain here in many ways, sorry mate
:-). I'm sure this is already very evident in your day to day w
o PostgreSQL directly, that isn't an API
contract we have commitments to - ie. we will change it underneath you
without warning or remorse today, even in a Z release :-).
ken.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscr
2-1.el6.noarch
> puppet-3.7.2-1.el6.noarch
> puppetdb-terminus-2.2.2-1.el6.noarch
> vim-puppet-2.7.20-1.el6.rf.noarch
>
>
> Did I miss a step somewhere?
Very likely you haven't restart your puppet master yet. Thats a
necessary step for the terminus upgrade to take hold,
st be using structured
facts and you must store the values as integers, they get stored in a
big int column, and the comparison will be uncoerced. Only signed big
int is supported today, there is no support for arbitrary precision
decimals.
ken.
--
You received this message because you are subs
lines and the quote I supplied above are here FYI:
https://docs.puppetlabs.com/community/community_guidelines.html#mailing-list-guidelines
ken.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emai
g
* store report
If none of that helps, we can explore turning on debug mode for Puppet
to see what's being logged.
ken.
--
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
nly in the
> default file locations. This is an architectural limitation."
>
> https://docs.puppetlabs.com/references/latest/type.html#nagioscommand
>
> i.e. if you set the target parameter, you lose the ability to purge.
Well spotted Jonathan ... :-).
So Kai, you can prov
ith resources
like nagios_host:
resources { "nagios_host":
purge => true,
}
ken.
--
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
in foreman. So my guess is that I'm good there.
Wait, are you actually purging the resources somewhere? If it becomes
unmanaged, that doesn't mean it cleans up after itself unless you are
purging also.
ken.
--
You received this message because you are subscribed to the Google G
if its coming from another place.
This is important, sometimes there is data coming from another node,
and its often what users don't expect. Make sure you check for typos
on the node name most importantly, this is the biggest contributing
factor to confusion around this :-).
ken.
--
You
g you to remake it when it needs a change. Starting
conservatively with what goes into the image I think is a good idea.
After that you'll start to see the wider problems when you run your
tests a lot ... such as the flakiness of public mirrors :-). But thats
a story for another day :-).
ken.
ls in CI for
example. This is because CI software such as Jenkins uses environment
variables as a primary API between the Jenkins job data and the jobs
scripts being executed.
https://github.com/puppetlabs/beaker/wiki/How-to-Write-a-Beaker-Test-for-a-Module
The BEAKER_set allows for a basic way
r perspective the helper gives you a rake task:
`rake spec` and a file like so:
https://github.com/puppetlabs/puppetlabs-puppetdb/blob/master/.fixtures.yml
that will help you automatically retrieve the other modules your
module depends on during testing time. As opposed to just running
`rsp
> That's great Ken.
>
> I'll have a look. My .fog file was correct but I was missing that
> ec2.yaml.
>
> I get the user experience thing, it'll evolve and I'll help if I can.
>
> Would I be right to assume you built your images with packer?
All of
ou are free to use the ones here, but if
you need customisation I'd suggest forking your own images :-).
Let me know how you get on with that. I think generally speaking all
of this needs an overhaul in regards to usability, a lot of this
awkward layout is due to backwards compatibility from legac
heavily so I'm happy to help you there, I know
some people use Google Compute Engine also, but I have no intimate
knowledge of how this one works.
ken.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this grou
ak.
FWIW also - I wouldn't test the state of the puppetdb module testing
pieces, we've been waiting for our QA & Module teams to automate those
tests for a about a year now :-(. But honestly, they haven't been ran
for quite some time - so I'd be dubious.
The PuppetDB source
code was written in a massive hurry,
and thus has very little error protection so if everything isn't spot
on, it might break.
ken.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving
> Thanks again for your help. I changed the password on a temporary basis to
> an absurdly simple one. I'm both happy to say that puppetdb is working now.
> And sad to have taken up your time with this. Sorry about that.
No problem mate, glad it was something simple in the
rd incorrectly or anything, but
the process of changing the password for the `puppetdb` pg user might
shake something up. I'm really grasping at straws, an incorrect
password error is usually just that ... but your tests don't align
with this potentiality :-). I guess what I'm saying
pe "help" for help.
>
> puppetdb=>
So this might potentially be a problem with your pg_hba.conf, I'm
guessing though.
Try the above again, but as the root user, not as postgres, and show
us the results.
Here is my pg_hba.conf fwiw:
https://gist.github.com/kbarber/0fd
its working its either using a different
database than we think it is, or potentially HSQLDB which is the
embedded one. You should be able to see clues if you are accidentally
using HSQLDB in this regard in /var/lib/puppetdb/db:
root@puppetdb1:~# ls /var/lib/puppetdb/db/
db.log db.properties db.s
> We do this, but could probably live without it. But we do it using the facts
> indirector and setting it up to cache to puppetdb.
So in both cases you use 'puppet facts upload'?
ken.
--
You received this message because you are subscribed to the Google Groups
"Pu
shipped with PostgreSQL. Maybe its a bug
in that package or pg_trgm is shipped separately?
I can probably take a look here. What distro and distro release is
this exactly? Is this the PG shipped with the distro or is it from
PGDG upstream?
ken.
--
You received this message because you are
, an example of what the data looks like and what you want
it to look like. I'm sure someone can then provide an example and an
explanation.
ken.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and st
support would be lovely.
ken.
--
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 discuss
inds of introspection
into what the web server is doing, much like you would with Apache,
but in a potentially more curated/monitoring prepared way (I'm not
trying to upset an Apache fans here, I love Apache as well, but we
couldn't easily embed it :-).
ken.
--
You received this message
ve to be a dev workflow, you just need to have the NREPL port
exposed in your PDB config.ini:
https://docs.puppetlabs.com/puppetdb/2.2/configure.html#repl-settings.
ken.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from
y (not to mention a C++11 based
facter will provide more portability opportunities).
The main complication as ever, is the SSL authentication and the PKI
handling of keys/certs etc. Obviously with Puppet you get the key/cert
signing baked in - although one might consider yet another tool or
bespoke m
or plugin for
example).
ken.
--
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
nning for 6-8 months.
Whatever this value is set to:
https://docs.puppetlabs.com/puppetdb/2.2/configure.html#report-ttl
Or the default, which is 14 days.
ken.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this g
standing this would help us
understand the priority of such a fix.
ken.
--
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...@goog
more detailed information and upgrade advice, consult the detailed
release notes here:
https://docs.puppetlabs.com/puppetdb/2.2/release_notes.html
Contributors
Brian Cain, Eric Timmerman, Justin Holguin, Ken Barber, Nick
Fagerlund, Ryan Senior and Wyatt Alt.
Changelog
-
Brian
ny core modules or core
resources, perhaps these are being introduced to a custom resource?
Can you also share a picture of your dashboard, so we can see the
duplication rate?
> Would that be the case, or is it something else I am not seeing ?
>
> Any ideas on how to improve this ?
you try logging a ticket here?
https://tickets.puppetlabs.com/browse/CLA
ken.
--
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...@googlegroup
uld need a list of distinct certificate names for both, and you
> would want to find the overlap between the two, using an intersection
> query for example
> (http://www.postgresql.org/docs/9.3/static/queries-union.html). None
> of this is supported by the PuppetDB query API today.
Con
1 - 100 of 656 matches
Mail list logo
