Puppet Community

can I get a review for <https://github.com/voxpupuli/puppet_metadata/pull/97>

I can create the Release PR but I’m not sure I have enough permissions to push it to the gem repository (never did it before)

yeah, I created it about 2 month ago.. before I got tasks on my new job :smile:

I’d still call it beta but.. better to release at least 0.0.1 so maybe someone will start using it :slightly_smiling_face:

shall I add it to some “managed” file so it get modulesynced?

we only have it for puppet-lint plugins, not for generic gems

cc <@U1PC2RAH0> <@U5V9MMW9E> <@U11HA7VJ7>

in the EU we are used to stupid decisions that get revoked or declined in court, I am not worried :D

&gt; “_where the main contributors to free and open-source projects are developers employed by commercial entities and when such developers or the employer can exercise control as to which modifications are accepted in the code base, the project should generally be considered to be of a commercial nature._”
This can be read to mean that if the main contributors are _not_ unemployed, then the project is commercially tainted

The "developer OR the employer can control" implicitly applies to anyone working on open source that is employed

That and the requirement to disclose vulns to ENISA within hours of discovery upends the entire vulnerability resolution process that exists today

(and could make ENISA a favorite place to visit by malicious actors if the info ends up being public)

good thing I'm unemployed. unfortunately, I no longer work on Puppet things

bastelfreak: doesn't look like a Puppet writing style guide but more from a branding / design perspective

bastelfreak: unexpectedly, kernel hacking, for this cloud-init project 

my partner finally got her driving license, so i don't need to sit in the car all the time, which means my brain works a lot better

I need to build up some stamina before I'm okay with cycling in this shite a weather 

my partner's got the office in town today, and i was doing childcare until now. now kiddo is gone to the grandparents, and I can do sensible things like laundry, and computer

instructions unclear, ended up hacking the washing machine?

Our puppetboard is not displaying facts on node pages, but the facts are clearly in the database because they are on the facts pages and show all the correct nodes. Any thoughts?

Found a 500 error
```ERROR:puppetboard.core:Exception on /node/dc4.example.com/facts/json [GET]
Traceback (most recent call last):
  File "/srv/puppetboard/virtenv-puppetboard/lib64/python3.9/site-packages/flask/app.py", line 2528, in wsgi_app
    response = self.full_dispatch_request()
  File "/srv/puppetboard/virtenv-puppetboard/lib64/python3.9/site-packages/flask/app.py", line 1825, in full_dispatch_request
    rv = self.handle_user_exception(e)
  File "/srv/puppetboard/virtenv-puppetboard/lib64/python3.9/site-packages/flask/app.py", line 1823, in full_dispatch_request
    rv = self.dispatch_request()
  File "/srv/puppetboard/virtenv-puppetboard/lib64/python3.9/site-packages/flask/app.py", line 1799, in dispatch_request
    return self.ensure_sync(self.view_functions[rule.endpoint])(**view_args)
  File "/srv/puppetboard/virtenv-puppetboard/lib64/python3.9/site-packages/puppetboard/views/facts.py", line 50, in fact_ajax
    if fact in app.config['GRAPH_FACTS'] and value is None and node is None:
TypeError: 'in &lt;string&gt;' requires string as left operand, not NoneType```

From the config: `GRAPH_FACTS = "architecture,puppetversion,osfamily"`

<https://github.com/voxpupuli/puppetboard/issues/907>

osfamily doesn’t exists on Puppet 8 I bet

not sure about other facts in the GRAPH_FACTS

theres a doc being produced to map this out in terms of legacy facts and replacements

aye they know about it and are advising its use

mhm didn't we merge that into puppet-lint cor

<https://github.com/puppetlabs/puppet-lint/blob/main/lib/puppet-lint/plugins/legacy_facts/legacy_facts.rb#L35-L104>

A fact that is in the list not existing shouldn't trigger this - it is checking each fact that does exist to see if it is in the list

<@U01E5GBFARF> are you able to provide a patch for this or track the issue down?