| 00:08.47 | *** join/#utah shanemhansen (~shansen@216.207.42.140) |
| 00:28.38 | *** join/#utah braxtron (~braxtron@63.228.208.98) |
| 02:46.33 | *** join/#utah josephscott (~josephsco@74.114.153.251) |
| 03:59.36 | *** join/#utah tiwula (~lane@174-23-2-196.slkc.qwest.net) |
| 04:29.58 | *** join/#utah tiwula (~lane@174-23-2-196.slkc.qwest.net) |
| 04:54.29 | klys | ~slashdot |
| 05:51.41 | *** join/#utah tiwula (~lane@174-23-2-196.slkc.qwest.net) |
| 08:53.00 | *** join/#utah Jantz (~IceChat9@2407:7000:8d04:100:4148:13fd:61dd:5a27) |
| 09:50.51 | *** join/#utah youtah_ (~youtah@67.139.187.132) |
| 09:53.55 | *** join/#utah youtah_ (~youtah@67.139.187.132) |
| 11:01.35 | *** join/#utah youtah (~youtah@67.139.187.132) |
| 11:04.21 | *** join/#utah youtah_ (~youtah@67.139.187.132) |
| 11:41.23 | *** join/#utah keldwud_ (~keldwud@199.192.164.75) |
| 12:49.06 | *** join/#utah Jantz (~IceChat9@118-93-140-161.dsl.dyn.ihug.co.nz) |
| 12:58.09 | *** join/#utah Jantz_ (~IceChat9@118-93-140-161.dsl.dyn.ihug.co.nz) |
| 13:10.48 | *** join/#utah Jantz (~IceChat9@2407:7000:8d04:100:4148:13fd:61dd:5a27) |
| 13:24.12 | *** join/#utah Jantz (~IceChat9@118-93-140-161.dsl.dyn.ihug.co.nz) |
| 13:42.48 | *** join/#utah Jantz (~IceChat9@118-93-140-161.dsl.dyn.ihug.co.nz) |
| 14:28.14 | *** join/#utah Jantz (~IceChat9@2407:7000:8d04:100:fca0:c755:a958:21ae) |
| 14:28.59 | *** join/#utah BLZbubba (~mark@pdpc/supporter/professional/blzbubba) |
| 14:45.39 | *** join/#utah Jantz (~IceChat9@2407:7000:8d04:100:fca0:c755:a958:21ae) |
| 14:49.08 | *** join/#utah tiwula (~lane@70.89.246.241-Busname-UT.hfc.comcastbusiness.net) |
| 15:07.40 | *** join/#utah josephscott (~josephsco@74.114.153.251) |
| 15:39.30 | *** join/#utah lane_ (~lane@70.89.246.241-Busname-UT.hfc.comcastbusiness.net) |
| 15:43.57 | *** join/#utah lane__ (~lane@70.89.246.241-Busname-UT.hfc.comcastbusiness.net) |
| 16:03.58 | *** join/#utah lane_ (~lane@70.89.246.241-Busname-UT.hfc.comcastbusiness.net) |
| 16:09.30 | *** join/#utah lane__ (~lane@70.89.246.241-Busname-UT.hfc.comcastbusiness.net) |
| 16:27.11 | *** join/#utah braxtron (~braxtron@216.160.248.178) |
| 16:31.39 | *** join/#utah youtah (~youtah@67.139.187.132) |
| 16:34.21 | *** join/#utah youtah_ (~youtah@67.139.187.132) |
| 16:44.04 | *** join/#utah lane_ (~lane@70.89.246.241-Busname-UT.hfc.comcastbusiness.net) |
| 16:54.36 | *** join/#utah lane__ (~lane@70.89.246.241-Busname-UT.hfc.comcastbusiness.net) |
| 17:16.41 | *** join/#utah youtah (~youtah@67.139.187.132) |
| 17:19.21 | *** join/#utah youtah_ (~youtah@67.139.187.132) |
| 17:24.24 | *** join/#utah lane_ (~lane@70.89.246.241-Busname-UT.hfc.comcastbusiness.net) |
| 17:34.08 | *** join/#utah lane__ (~lane@70.89.246.241-Busname-UT.hfc.comcastbusiness.net) |
| 17:44.23 | *** join/#utah lane_ (~lane@70.89.246.241-Busname-UT.hfc.comcastbusiness.net) |
| 17:48.57 | *** join/#utah lane__ (~lane@70.89.246.241-Busname-UT.hfc.comcastbusiness.net) |
| 18:04.34 | *** join/#utah lane_ (~lane@70.89.246.241-Busname-UT.hfc.comcastbusiness.net) |
| 18:09.10 | *** join/#utah lane__ (~lane@70.89.246.241-Busname-UT.hfc.comcastbusiness.net) |
| 18:39.03 | *** join/#utah lane_ (~lane@70.89.246.241-Busname-UT.hfc.comcastbusiness.net) |
| 18:43.56 | *** join/#utah lane__ (~lane@70.89.246.241-Busname-UT.hfc.comcastbusiness.net) |
| 19:19.13 | jfindlay | jlp_znc: do you know if puppet has the equivalent of salt's onchanges requisite? (https://docs.saltstack.com/en/latest/ref/states/requisites.html#onchanges) |
| 19:25.12 | jlp_znc | I don't know... but it looks like a cool feature. maybe goozbach would know (if he were on here). |
| 19:25.38 | jlp_znc | I've been using chef for the last year... as far as I know, it does not have that capability. |
| 19:28.14 | jfindlay | sigh |
| 19:29.01 | jfindlay | puppets requisite system seems to be inferior |
| 19:29.04 | joshh | have you looked at subscribe and notify? |
| 19:29.16 | joshh | it probably is inferior but you might be able to make it do what you need |
| 19:29.52 | joshh | err not notify7 |
| 19:31.02 | joshh | well a lot of resources/types do have a notify attr that can restart a service or something |
| 19:31.10 | jfindlay | I need to only run a script if a package was updated. Maybe I should just include the script in a post install hook |
| 19:31.52 | jfindlay | the problem is that the script interacts with resources external to the system that may need to be parameterized |
| 19:31.58 | joshh | yes you can do that |
| 19:32.15 | joshh | do an exec for the script, and have it subscribe to the package |
| 19:33.02 | jfindlay | like this? https://ask.puppet.com/question/17036/notify-and-subscribe-with-refreshonly-not-working-in-exec-resource/ |
| 19:34.15 | joshh | more like this |
| 19:34.24 | joshh | https://stackoverflow.com/questions/53295115/subscribe-to-packages-in-puppet |
| 19:34.47 | joshh | except that you do want your script to run every time |
| 19:35.48 | jfindlay | actually I only want my script to run if the package is updated |
| 19:35.54 | jfindlay | like salt's onchanges requisite |
| 19:36.16 | jfindlay | if the state is applied and the package does not update, the script should not run |
| 19:36.17 | joshh | so not after the initial install? |
| 19:37.01 | jfindlay | I guess by updated I mean if any action is taken by the package { $pkg: ensure => 'latest'} state |
| 19:37.33 | joshh | subscribe would run the command after the first install and all updates |
| 19:41.46 | jfindlay | so, subscribe and refreshonly on the exec resource? |
| 19:43.00 | joshh | yes |
| 19:44.10 | jfindlay | thanks |
| 19:44.21 | joshh | np |
| 19:44.26 | joshh | hopefully it works right for you |
| 19:45.22 | jfindlay | this seems to be the intended mechanism, and it will be better than what I was considering otherwise |
| 21:02.03 | jfindlay | joshh: do you know where or how $module_name is defined? |
| 21:04.32 | joshh | looks like a built in compiler variable |
| 21:04.46 | joshh | https://puppet.com/docs/puppet/5.0/lang_facts_and_builtin_vars.html#compiler-variables |
| 21:07.32 | jfindlay | I've seen this pattern many times: `content => template($module_name/my_file.erb)` |
| 21:08.15 | jfindlay | where `my_file.erb` actually lives at `my_module/templates/my_file.erb` |
| 21:08.22 | joshh | the module_name should be optional there |
| 21:08.44 | joshh | ive actually never seen it in person |
| 21:09.22 | joshh | oh |
| 21:09.31 | joshh | actually it looks like just using the module name is common |
| 21:09.36 | joshh | but that should work too |
| 21:09.48 | jfindlay | If I have a file that does not need to be templated, can I just use `content => puppet:///my_module/files/my_file`? |
| 21:10.13 | joshh | you can either use a file resource, and put it in the files dir instead of templates |
| 21:10.31 | joshh | or have the content attr be static content, a variable, etc |
| 21:11.15 | jfindlay | joshh: if it's not too hard, can you point me to documentation on using a file resource? |
| 21:11.38 | joshh | ya, it's basically the same as the template though, except you call it a file, and the attr is source instead of content |
| 21:11.52 | jfindlay | so like in the `file` resource docs? |
| 21:12.07 | joshh | exactly |
| 21:12.15 | jfindlay | aha |
| 21:12.22 | jfindlay | thanks |
| 21:13.25 | joshh | you can actually use content rather than source with files also, but nobody does unless it's something simple |
| 21:14.04 | jfindlay | do you know if it's possible to apply a module to a system without having to go through the master, in the same way you can with a manifest: `puppet apply /path/to/manifest.pp`? |
| 21:14.31 | joshh | if you have the manifests locally then you just do puppet apply |
| 21:14.39 | *** part/#utah keldwud_ (~keldwud@199.192.164.75) |
| 21:14.46 | joshh | the manifest is what would refer to the module |
| 21:14.58 | joshh | so you would need it where the manifest can find it |
| 21:15.08 | *** join/#utah keldwud (~keldwud@unaffiliated/keldwud) |
| 21:16.08 | joshh | or you could just do everything directly in a manifest without a module |
| 21:17.59 | keldwud | omg, the server / agent communication issue I was having last week? |
| 21:18.09 | keldwud | the reason the authentication portion succeeded was because I manually put in the IP address. apparently after authenticaiton, it performs a dns lookup or something and configured itself with in IP address that was just one digit different than the ip address of the manager |
| 21:18.15 | keldwud | so when I looked at the logs, I could see it trying to connect |
| 21:18.21 | keldwud | but failed to realize that it was trying to connect to the wrong host |
| 21:18.41 | keldwud | x.x.x.abc vs x.x.x.abd |
| 21:18.46 | keldwud | facepalms |
| 21:18.58 | keldwud | does that ever happen to you guys? |
| 21:20.18 | joshh | all the time |
| 21:20.38 | joshh | not exactly that, but various mistakes |
| 21:20.45 | joshh | just gotta be careful |
| 21:21.28 | keldwud | yeah, here I was thinking I was smart, troubleshooting all the different htings that could have caused the lack of traffic |
| 21:21.42 | keldwud | except for actually notcing that the logs were telling me it was connecting to elsewhere |
| 21:21.50 | keldwud | took my co-worker's eyes to see it |
| 21:22.06 | keldwud | that's why we team up sometimes! peer review is worth its weight in gold |
| 21:23.08 | jlp_znc | yes... I have lost count of the times someone has looked over my shoulder and said "um, why is that a dot instead of a comma" or something similar. |
| 21:23.22 | jlp_znc | I stare at it for hours, they find the problem in minutes. |
| 21:23.42 | jlp_znc | I've done it the other way too (where I'm the one who glances at it ans says "um, is that the right variable there?" |
| 21:24.50 | joshh | tons of my code reviews are just correcting people's typos and dyslexia |
| 21:25.15 | joshh | its always weird when someone's comments are full of mistakes and bad grammar though and i don't want the review to be nothing but comment grammar policing |
| 22:28.56 | keldwud | joshh I view it this way, if they're lazy with their English grammar and punctuation, how can I trust them to pay attention to detail when it comes to configuration files and code? |
| 22:34.51 | joshh | its not the same though for some reason |
| 22:35.30 | *** join/#utah Jantz (~IceChat9@2407:7000:8d04:100:4033:79d0:9aa2:ffd8) |
| 22:56.57 | jfindlay | so I could probably create a simple manifest that references a module? I didn't think of this before. I need to package what I'm doing into a module in order to integrate it into an existing system, but don't really have a way to test it |
| 23:00.31 | joshh | test how? there is rspec style testing that's standard for it, similar to chef |
| 23:01.14 | joshh | but yes modules are just for organizing code and manifests are the main entry points |
| 23:03.12 | joshh | you can also run it in noop mode, to see the changes without applying |
| 23:46.39 | *** join/#utah Jantz (~IceChat9@2407:7000:8d04:100:4033:79d0:9aa2:ffd8) |