20:00:08 #startmeeting Ansible Windows Working Group 20:00:08 Meeting started Tue Jun 11 20:00:08 2019 UTC. 20:00:08 This meeting is logged and archived in a public location. 20:00:08 The chair is jborean93. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:00:08 Useful Commands: #action #agreed #halp #info #idea #link #topic. 20:00:08 The meeting name has been set to 'ansible_windows_working_group' 20:00:09 nitzmahone: Error: Can't start another meeting, one is in progress. 20:00:13 heh 20:00:13 bah 20:00:16 #chair nitzmahone 20:00:16 Current chairs: jborean93 nitzmahone 20:00:18 lol 20:00:19 heya 20:00:24 #chair jhawkesworth 20:00:24 Current chairs: jborean93 jhawkesworth nitzmahone 20:00:26 hey 20:01:26 give it a few more minutes before starting 20:05:02 looks like it is just us 20:05:06 nothing on the agenda so... 20:05:09 #topic open floor 20:05:14 anything to talk about? 20:05:44 nothing windowsy for me this week. Been wrestling with network devices 20:06:23 There was the question earlier about the auto-conditional reboot thing; my original intent there was to wrap that up in a module_util that could be shared for facts as well (eg `pending_reboot: true`) 20:06:58 that's a nice idea 20:07:01 I don't mind having it there, so long as we're using the same bit of code to determine it anyplace we need to do a conditional reboot like that 20:08:22 For win_reboot, I still think the default should be "just reboot", but I'm not opposed to a new arg that would allow someone to opt into the "only if the pending_reboot flag is true" kind of behavior 20:08:51 definitely keep default as always reboot 20:08:54 yep 20:09:34 nothing else burning on my sid 20:09:36 *side 20:09:45 are you sure it was a typo? 20:09:52 :P 20:09:56 :-) 20:10:30 wondering how much use that option would be. 20:11:09 in my playbooks I usually know / have to take control of when I need to reboot it. 20:11:44 not opposed to having it as an option. 20:11:46 Yeah, the only thing I could see it being useful for is clearing the "I'm going to do something else that won't work if there's a pending reboot" case 20:12:20 In that case, having it as a fact usable in a conditional would probably suffice anyway 20:12:20 might make grokking what has gone easier if it could actualy set 'skipped' status for the module results. although I can't think of anywhere I've ever seen do that 20:12:53 Modules can self-skip- tis how `supports_check_mode: false` is implemented 20:13:06 otherwise its 'hey that reboot took 1 second, how come this one took 90seconds' 20:13:39 I guess in the use case I'm thinking of, making it conditional with a fact should suffice (and is more flexible to boot) 20:14:05 cool I must have known that once 20:14:45 hmm RagingBuffalo no longer around to ask 20:14:46 Learn a new phone number, forget a useless bit of Ansible trivia- tis the way it goes ;) 20:15:13 That statement is somewhat dated, since I never learn new phone numbers anymore 20:15:42 remind me, what's a phone again :-) 20:15:46 the fact seems like the more flexible option 20:15:51 i just use QR codes 20:16:21 * nitzmahone reminds self to send bcoca some nefarious QR codes ;) 20:18:26 I guess using the fact is less intuitive than looking for a module to do it. I guess an example in win_reboot docs would fix that for most though 20:18:58 docs are good, we could always add the option for it to gather the fact itself, gives people both options 20:20:28 that's nice. 20:24:25 cool if there is nothing else, will close the meeting 20:24:47 nothing from me. cheers 20:26:10 awesome, have a good one all 20:26:13 #endmeeting