https://www.puppet.com/community logo
Join Slack
Powered by
# office-hours
  • g
    What would the synatx be for referingto another class resource defined like: class skolv_nrpe.... { exec { 'reload_nrpe': .... } } Something like this....? file { $op5_nrpe_cfg: ensure => file, ... notify => Exec[ skolv_nrpe::exec[reload_nrpe'] ], }
  • g
    What would the synatx be for referingto another class resource defined like: class skolv_nrpe.... { exec { 'reload_nrpe': .... } } Something like this....? class another_class { file { $op5_nrpe_cfg: ensure => file, ... notify => Exec[ skolv_nrpe::exec[reload_nrpe'] ], } }
  • g
    What would the synatx be for referingto another class resource defined like: class skolv_nrpe.... { exec { 'reload_nrpe': .... } } Something like this....? class another_class { file { $op5_nrpe_cfg: ensure => file, ... notify => Exec[ skolv_nrpe::exec['reload_nrpe'] ], } }
  • g
    That saved my afternoon! 😄
  • d
    goodnews 🧑‍🏫 Bolt is about to start up in 15 minutes
  • c
    Hello everyone! Its Bolt office hour. bolt
  • m
    Hi Cas, I would like to ask what is the roadmap for Bolt? In 2022 there was only 1 new release of Bolt and a small bugfix release after that but nothing more than that. As end user of Bolt it seems to me that Bolt has grinded to a halt in terms of development?
  • m
    Hi Cas, I would like to ask what is the roadmap for Bolt? In 2022 there was only 1 new release of Bolt and a small bugfix release after that but nothing more than that. As end user of Bolt it seems to me that Bolt has grinded to a halt in terms of development?
  • c
    Great question!
  • c
    We are working with our internal product team to come up with a roadmap for Bolt.
  • c
    Once we have more information we will share it. My team has been working on prioritizing some Bolt development lately. We will be pushing a release soon with packages for some new platforms and several bug fixes.
  • m
    That would be great 🙂
  • c
    Are there any "big" features you are looking for in particular?
  • s
    This message was deleted.
    m
    c
    • 3
    • 8
  • s
    This message was deleted.
    c
    b
    m
    • 4
    • 20
  • m
  • c
    Yes @Mischa Coenen we appreciate you raising those. They were very helpful in the discussion with our product team. We are going to get those prioritized soon
    🙌 1
  • b
  • b
  • d
    beaker _🦊Vox Pupuli monthly sync; see calendar event for info_ is about to start up in -15 minutes
  • d
    allthethings Next up is 🧑‍🏫Puppet Core Team in 1 hours
  • d
    indeed 🧑‍🏫Puppet Core Team is about to start up in 15 minutes
  • j
    Hi folks, Core office hours are open! Have a question about open source puppet or Puppet Platform 6 & 7 releases, ask away!
  • b
    hey @josh! I was talking with some Vox people earlier and we were speculating about the deferred functions work in flight. Do you anticipate that will change agent compatibility when it lands?
  • j
    We're working on two changes, one on the server, the other on the agent. The agent change is to allow deferred functions to follow normal puppet relationships/ordering. For puppet 6.x & 7.x, we're planning on adding a puppet setting so users can opt-in to the "lazy" behavior.
  • j
    We're working on two changes, one on the server, the other on the agent. The agent change is to allow deferred functions to follow normal puppet relationships/ordering. For puppet 6.x & 7.x, we're planning on adding a puppet setting so users can opt-in to the "lazy" behavior.
  • b
    would lazy eval be all on the agent side? (ie, it would be catalog compatible with prior versions of the server)
  • j
    Yeah lazy eval is all agent side. There aren't any catalog changes or issues of agent/server compatibility.
    👍 1
  • b
    nice
  • j
12345...78Latest