https://www.puppet.com/community logo
Join Slack
Powered by
# office-hours
  • b
    I don't 😞
  • j
    The second part of the puzzle is that the agent needs to stop collecting legacy facts in the first place (https://tickets.puppetlabs.com/browse/PUP-8543) However, many builtin providers still rely on legacy facts, like https://github.com/puppetlabs/puppet/blob/e95386bbcb2b4eefb898fd83ac47eaec3bbeb021/lib/puppet/provider/service/init.rb#L24
  • j
    The second part of the puzzle is that the agent needs to stop collecting legacy facts in the first place (https://tickets.puppetlabs.com/browse/PUP-8543) However, many builtin providers still rely on legacy facts, like https://github.com/puppetlabs/puppet/blob/e95386bbcb2b4eefb898fd83ac47eaec3bbeb021/lib/puppet/provider/service/init.rb#L24
  • j
    So the plan is to switch those over to using structured facts in puppet 8
  • s
    This message was deleted.
    y
    j
    b
    • 4
    • 13
  • b
    ah. I thought that's planned for 7 already
  • j
    I don't think we can make that change in puppet 7 due to the way rspec-puppet stubs out facts to change provider confine and suitability. For example, if a test stubs 
    lsbdistrelease
    but not 
    os.distro.release.full
    then the test will break
  • b
    ah mhm
  • b
    rpsec-puppet-facts should really be mandatory for unit tests
  • j
    I think the only way we could land something like that in puppet 7 is if it was opt-in and puppet automatically translated from legacy to structured facts like https://github.com/mmckinst/puppet-lint-legacy_facts-check/blob/2fe12beff2c7c764f13303c46338fe9f7d6642fa/lib/puppet-lint/plugins/legacy_facts.rb#L29-L98
  • j
    I think the only way we could land something like that in puppet 7 is if it was opt-in and puppet automatically translated from legacy to structured facts like https://github.com/mmckinst/puppet-lint-legacy_facts-check/blob/2fe12beff2c7c764f13303c46338fe9f7d6642fa/lib/puppet-lint/plugins/legacy_facts.rb#L29-L98
  • j
    But that's a lot of work for not much gain. As in, the biggest problems with legacy facts are solved by not sending them to puppetserver & puppetdb.
  • j
  • j
    hmm, I think the "projected July 2023" is incorrect. I'll need to check with some folks on that.
  • j
  • b
    ah right, now I remember 😄
  • d
    fry dancing Next up is 🧑‍🏫 Bolt in 4 hours
  • j
    Alright folks, that's a wrap, see you in two weeks!
    thanks 2
  • d
    letsplay 🧑‍🏫 Bolt is about to start up in 15 minutes
  • c
    Hey everyone! Here to talk Bolt for the next hour
  • d
    letsplay Next up is 🧑‍🏫Puppet Forge in 43 hours
  • d
    hello Am Daniel
    👋 2
    👋🏼 1
  • y
    Speaking of legacy facts.. I’d say modules using legacy facts should be specifically tagged on Puppet Forge. This can give some motivation to fix them (if module is still maintained)
    👍 1
  • d
    fry dancing 🧑‍🏫Puppet Forge is about to start up in 15 minutes
  • d
    goodnews Next up is 🧑‍🏫PE Console in 170 hours
  • d
    beaker 🧑🏫PE Console is about to start up in 15 minutes
  • s
    \o Good day y’all - console office hour has begun!
  • s
    If you have any questions/suggestions for anything related to the console, any of the console services (RBAC, Classifier, Activity Service) or the Orchestrator, ask away.
  • d
    waiting Next up is 🧑‍🏫Puppet Core Team in 115 hours
  • s
    OK, that’s a wrap for today - we’ll be back in a couple of weeks. Y’all be good to yourselves.
1...293031...78Latest