Puppet Community

`puppet query 'inventory { trusted.extensions.pp_whatever = "value" }'`

that gives me all infos about nodes that have this extension

I just want a unique list of values for the extension

<@U1PC2RAH0> <@U012ASYJN0L>
`puppet query 'inventory[trusted.extensions.pp_whatever]{ trusted.extensions.pp_whatever = "value" group by trusted.extensions.pp_whatever }'`

that also filters for a specific value, in this case `value`. so I just get a single result

So what do you mean? Like having an extension called `pp_whatever` with the value `"value"`. What kind of filter you need?

I want a list of all the different values I have in the database, for a specific trusted fact

```$ puppet query 'facts[value]{ name = "operatingsystem" group by value}'
[
  {
    "value": "CentOS"
  },
  {
    "value": "Rocky"
  }
]```

just not for facts, but for trusted facts

Yes sure that is what the `pp_whatever` stands for external `trusted.extensions.customer`  then you get all uniqe customers

`inventory[trusted.domain]{ group by trusted.domain }`
Gets you all trusted domains

I thought for `group by` I need another filter

No just the value itself. At least the doc does it too :sweat_smile:
<https://www.puppet.com/docs/puppetdb/8/api/query/v4/pql.html#group-by>

&gt; ```inventory[trusted.domain]{ group by trusted.domain }```
&gt; Gets you all trusted domains
JFYI: Since i also just found it out: That is also working to get values inside a structured fact and works also with the trusted one.
```fact_contents[value] { path = ["trusted","domain"] group by value }```
At least when the `trusted` of `inventory` is the same as the `trusted` inside `facts` what it must be since no additional information are there.

someone has an idea how to do that for trusted facts?

those aren't supported by the facts endpoint

“Subquery against /fact-contents to get all remotely authenticated trusted facts” Not sure how/if that works with PQL though 

Maybe solution in <https://groups.google.com/g/puppet-users/c/rh2nAvmtcWg|https://groups.google.com/g/puppet-users/c/rh2nAvmtcWg> ??

regarding providers: garrys post is still valid. new api has several limitations like missing noop capability

Hi again! Back to my original question about managing DNF modules via Puppet:
Would this go better into the existing <https://forge.puppet.com/modules/puppet/yum/readme|puppet-yum> module, or in a separate one?

See the `puppet-yum` module at <https://forge.puppet.com/puppet/yum?src=slack&amp;channel=voxpupuli>

cruelsmith: I'd say in the existing yum unless it conflicts in someway.

And on a related note - <https://github.com/voxpupuli/puppet-yum/pull/308> would be good to green up some other MRs.

frisbee: ha! I wanted to ping you about the idea from emerson_prado, but forgot our IRC handle

someone has a function that can download a file and returns the content as multiline string?

I would like to turn <https://github.com/bastelfreak.keys> into ssh_authorized_keys resources

<https://github.com/voxpupuli/puppet-extlib/blob/master/lib/puppet/functions/extlib/read_url.rb> ha!

frisbee: I'm pretty sure it doesn't conflict, so I'll start writing more focused and clean code to manage dnf modules into yum module. Thanks!

hmm I wonder what this is good for <https://github.com/hashicorp/vault/pull/20595>

Hey there :wave:! Would it be possible to have some eyes on the ongoing <https://github.com/puppetlabs/puppetlabs-stdlib/pull/1307|puppetlabs-stdlib Puppet 8 update>? We (the CaT team at Puppet) would like to know the opinion of Voxpopuli on the current state of the update and, more particularly, on the possible deprecation of the uriescape.rb function. While early scans seem to suggest that this function is no longer impactful in our modules/tools, we would like to know whether the community is happy enough with this deprecation.

See the `puppetlabs-stdlib` module at <https://forge.puppet.com/puppetlabs/stdlib?src=slack&amp;channel=voxpupuli>

We are also looking into deprecating parsepson.rb. This is a natural follow up to Puppets 8 general PSON removal.

I am pro deprecation as well, this functionality should be migrated into an apilib of some sort (which might be a submodule of stdlib to create, but that would allow someone to make https api calls from puppet server for various effects)

+1 for deprecation. If one still needs them maybe we can migrate them to extlib?

<https://www.bleepingcomputer.com/news/security/github-now-auto-blocks-token-and-api-key-leaks-for-all-repos/>

I know I must be annoying someone by now :P but can someone with merge capabilities look at the PRs for <https://github.com/voxpupuli/puppet-openssl> ? I would argue merging all backwards incompatible before making a major release for puppet7 would be the path of least resistance :P

zilchms: please check comments in <https://github.com/voxpupuli/puppet-openssl/pull/159/files#diff-b55cd2d4fee4ad88a9e21316ff2015c5579e8ec9bef7bc0fe5253262905fa702R50>

then please rebase <https://github.com/voxpupuli/puppet-openssl/pull/153> and try to add a more meaningful title