Great ...Thanks

hello, They exist a solution for drop some native fact like

scope6_xxx

? That create lot of fact for a duplicate content

pdb/query/v4/facts | jq '[.[] | select(.name | test("^scope6_")) | .name] | length'        
16942

hello, They exist a solution for drop some native fact like

scope6_xxx

? That create lot of fact for a duplicate content

pdb/query/v4/facts | jq '[.[] | select(.name | test("^scope6_")) | .name] | length'        
16942

https://puppet.com/docs/puppetdb/7/configure.html#facts-blocklist you can block what puppetdb inserts into the database. also facter.conf has a blocklist

so with

facts-blocklist

I can still use the fact on my puppetcode ?

I don't think so. how do you want to use it when it's blocked?

No I'm ok with that, just a simple question 🙂

do you have any performance issues? Otherwise I would keep it as is

ty @bastelfreak

This message was deleted.

This message was deleted.

Should I create a new issue similar to https://github.com/puppetlabs/pdk/issues/538 ?

Interesting... I think we might have to stick with exported resources for now because right now things are classified via node-scope variables, which I don't think I'd be able to select on, but this makes a good case for future improvements. Thanks!

So I'm using the

puppet debugger

as suggested yesterday, to test a custom function. The problem is the custom function doesn't exist in the current environment. or any environment. How do i tell the

puppet debugger

about the custom function so I can run it interactively? (I can see the list of functions available. None of them are the custom ones.)

what do I need to include to see the function?

This message was deleted.

I've been a long time puppet user (2013-ish) and since I've never really followed best practices, I was gonna try and rejuvenate my puppet environment. Right now I'm on puppet 5.5 and I was gonna start fresh on puppet 7 To make things easier to install and upgrade, I was gonna leverage my existing kubernetes cluster and use the helm chart provided by puppetlabs: https://github.com/puppetlabs/puppetserver-helm-chart/ Installing version 6.5.1 of the chart failed in the init container, due to a bug I already sent a PR for: https://github.com/puppetlabs/puppetserver-helm-chart/pull/128

I've been a long time puppet user (2013-ish) and since I've never really followed best practices, I was gonna try and rejuvenate my puppet environment. Right now I'm on puppet 5.5 and I was gonna start fresh on puppet 7 To make things easier to install and upgrade, I was gonna leverage my existing kubernetes cluster and use the helm chart provided by puppetlabs: https://github.com/puppetlabs/puppetserver-helm-chart/ Installing version 6.5.1 of the chart failed in the init container, due to a bug I already sent a PR for: https://github.com/puppetlabs/puppetserver-helm-chart/pull/128 I can install 6.4.0 and it passes readiness. If I install 6.5.x, the pod of the puppetserver-puppetserver-master deployment does not pass readiness, even though I can curl the port that's configured there. Here's the curl command I'm running: curl -v --insecure https://127.0.0.1:8140/status/v1/simple The presented certificate is not publicly signed, but according to the kubernetes manual that is not an issue since certs aren't verified.

I've been a long time puppet user (2013-ish) and since I've never really followed best practices, I was gonna try and rejuvenate my puppet environment. Right now I'm on puppet 5.5 and I was gonna start fresh on puppet 7 To make things easier to install and upgrade, I was gonna leverage my existing kubernetes cluster and use the helm chart provided by puppetlabs: https://github.com/puppetlabs/puppetserver-helm-chart/ Installing version 6.5.1 of the chart failed in the init container, due to a bug I already sent a PR for: https://github.com/puppetlabs/puppetserver-helm-chart/pull/128 I can install 6.4.0 and it passes readiness. If I install 6.5.x, the pod of the puppetserver-puppetserver-master deployment does not pass readiness, even though I can curl the port that's configured there. Here's the curl command I'm running: curl -v --insecure https://127.0.0.1:8140/status/v1/simple The presented certificate is not publicly signed, but according to the kubernetes manual that is not an issue since certs aren't verified.

I've been a long time puppet user (2013-ish) and since I've never really followed best practices, I was gonna try and rejuvenate my puppet environment. Right now I'm on puppet 5.5 and I was gonna start fresh on puppet 7 To make things easier to install and upgrade, I was gonna leverage my existing kubernetes cluster and use the helm chart provided by puppetlabs: https://github.com/puppetlabs/puppetserver-helm-chart/ Installing version 6.5.1 of the chart failed in the init container, due to a bug I already sent a PR for: https://github.com/puppetlabs/puppetserver-helm-chart/pull/128 I can install 6.4.0 and it passes readiness. If I install 6.5.x, the pod of the puppetserver-puppetserver-master deployment does not pass readiness, even though I can curl port 8140. Here's the curl command I'm running: curl -v --insecure https://127.0.0.1:8140/status/v1/simple The presented certificate is not publicly signed, but according to the kubernetes manual that is not an issue since certs aren't verified.

This message was deleted.

Here's the definition of the readiness probe: https://github.com/puppetlabs/puppetserver-helm-chart/blob/v6.5.1/templates/puppetserver-deployment-masters.yaml#L207-L211 Here's what it looks like in kubectl describe: Readiness: http-get https//8140/status/v1/simple delay=0s timeout=20s period=60s #success=1 #failure=3

@hbui Here's the definition of the readiness probe: https://github.com/puppetlabs/puppetserver-helm-chart/blob/v6.5.1/templates/puppetserver-deployment-masters.yaml#L207-L211 Here's what it looks like in kubectl describe: Readiness: http-get https//8140/status/v1/simple delay=0s timeout=20s period=60s #success=1 #failure=3

message has been deleted

puppet node status test1001 fails with Error: Could not retrieve status for test1001: Failed to find '/pdb/query/v4/nodes/test1001' on any of the following 'server_urls' (insert url here)

i'm trying to test to see if there is information in my puppetdb after installing it and getting it running

test1001 is the hostname of one of my agents that have checked in

the https:(insert url here) is in my puppetdb.conf

Is your db host blocking connections?

my db is on my master which.. is talking to my agents