but that really confused me

you should have an invitation

damned, more legal terms to read in a google doc :-(

'You have no right' [Accept]

:-)

Should be good!

:D

I was working on adding puppet 8 generated facts to facterdb and was well underway when it looked like there was a PR to remove legacy facts that hasn't been merged. Should I continue on or is there other information I should have?

ah mhm, legacy facts

I say new puppet 8 facts should not have legacy facts

if that turns out to be a requirement we can add them later

good to know

@Craig Gumbley @josh ^ what are your expectations for facterdb on puppet 8 facts?

is there even a new facter release?

ah 4.4

I'm not seeing much by the way of 4.3 factsets either

@bastelfreak shall we finish up the PRs that were started on to make it an rspec-puppet configurable?

Since facter 4.4 ships in both puppet 7 and 8, would it make sense to continue generating legacy and structured facts in facterdb, and prune out the legacy facts when running rspec tests in the context of puppet 8?

oh are there?

This message was deleted.

@josh I agree, yes

I think that was the plan. Default to pruning them on puppet 8.

Cool notit

this seems better since folks have the ability to turn them back on for 8 and still presumably need to do unit testing on old codebases

we certainly have a lot of cleanup to do around legacy facts at $JOB

smortex: ha nice, I setup codersrank because I saw it in your profile. https://profile.codersrank.io/leaderboard/developer?country=Germany&technology=Puppet :D

fires up actual computer

:-) Nice! I like to know that my go + js experience is basically the same as the one I have with yacc. This help me tell people why I should not touch their website.

:D

I've no clue why there is so much html