[11:56:14] <godog>	 hi, I'm adding a class that will need to run a service (prometheus-pushgateway), is there a recommendation/guideline on using service{} vs systemd::service{} vs sth else ?
[11:56:42] <godog>	 I've seen both quite a bit tho
[12:06:20] <jbond42>	 godog: systemd::service requires you pass the content of the systemd unit file so is cood to use if there is not allready a service dfinition.  if there is allready a service definition i.e. the package installed a valid systemd unit then i would just use service
[12:10:12] <godog>	 jbond42: ack, makes sense, thank you!
[12:10:28] <godog>	 in this case I'll likely customise the unit anyways
[12:14:49] <jbond42>	 ack systemd::service sounds like the best candidte.  also worth mentioning that if there is allready a systemd file and you just need to override/add a small snippit then you can set override => true e.g. systemd::service{ 'foo': content=> 'override'; override => true}
[12:26:18] <godog>	 indeed! that's handy
[13:35:06] <XioNoX>	 "Is it possible to have an ical feed with all the planned maintenance related to our circuits?"
[13:35:06] <XioNoX>	 Telia: "We do not have this in our current system, but when we go live with the new one we do. we will keep you updated about it once its implemented"
[13:35:06] <XioNoX>	 NTT: "No"
[13:35:06] <XioNoX>	 Lumen: No answer
[15:31:17] <lmata>	 cdanis i see a PostMortem grouplet session for monday, would you mind if I crash that? 
[15:31:23] <lmata>	 :D
[20:09:14] <effie>	 lmata: you are on the invitation :)
[20:12:28] <cdanis>	 yeah, sorry, I did that but forgot to post here
[21:09:32] <lmata>	 Thanks 😊