20:00:41 #startmeeting Ansible Windows Working Group 20:00:41 Meeting started Tue Jan 7 20:00:41 2020 UTC. 20:00:41 This meeting is logged and archived in a public location. 20:00:41 The chair is nitzmahone. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:00:41 Useful Commands: #action #agreed #halp #info #idea #link #topic. 20:00:41 The meeting name has been set to 'ansible_windows_working_group' 20:00:51 * jhawkesworth lurking / mobile. Bedtime overrunning 20:03:05 #topic open floor 20:03:28 #info 2.9 service release next week 20:03:48 Good to know 20:04:01 Happy New year, BTW 20:04:04 Same! 20:04:21 * nitzmahone will wait for a couple minutes to see if anyone wants to discuss 20:04:43 howdy 20:04:50 * bcoca waves 20:04:54 Heya 20:05:15 Actually do we want to mention the 2008 thoughts? 20:05:18 fyi, we have PR updating behaviour of no_log for python modules, not sure what windows impelentation does 20:05:52 bcoca: what's the change 20:05:56 https://github.com/ansible/ansible/pull/64733 20:05:59 nitmzahone: probably a good idea 20:06:25 basically allow no_log=false to override the warning on 'password/secret optoin detection that is missing no_log' 20:07:04 So I'll bring it up again next week, but we're thinking about deprecating official support for Server 2008/R2- not to actively break anything, but getting it out of CI and not including it in new feature development 20:07:04 hmm I will have to look to see if I implemented that part 20:07:19 why i brought up here ;-p 20:07:59 nitzmahone: what is M$ support cycle? 10yrs? 20:08:18 Keeping 2008/R2 running in CI will become increasingly difficult, since Azure will be the only "officially supported" place for it now that it's dead 20:08:18 technically ends on the 14th 20:08:18 but it stays on life support on Azure for 3 years 20:08:18 bcoca: it varies, and they change their minds all the time and extend things 20:08:44 he 20:09:10 I was hoping to kill off our win 7 but some clients going for extended support so worth checking paying customer situation 20:09:54 desktop side is harder, people really dont want to upgrade 20:10:11 That one's never been officially supported anyway 20:10:11 server side at least you can count on IT depts wanting to have patches 20:10:14 bcoca: we do not do that in the Ansible.Basic.cs for no_log 20:10:52 jborean93: i imagined that much, the 'is this option a secret w/o no_log setting' heuristics is someting i would avoid if possible (and i wrote it ...) 20:11:26 I'm not clear how they're handling the patch situation, like if patches will only be available on Azure, but it kinda sounds like it 20:11:26 just wanted to make sure we kept 'current parity' 20:12:02 heh, yeah, the heuristic thing is both an endless game of whack-a-mole and potential for false positive 20:12:30 there is a small amount of that heuristics in the C# stuff but definitely not as much as Python 20:12:37 mostly was if someone wants to shoot themselves in the foot then so be it 20:12:46 killed all our S2008. If s2003 is anything to go by, some critical patches went out long after support ended iirc 20:13:00 sadly i had to add due to CVE strom ... but this change lets people shoot themselves in foot .. knowingly 20:13:03 which im fine with 20:14:30 OK, if nothing else, we'll call it til next week... 20:14:44 +1 20:15:25 Thanks for being here, and happy new year! 20:15:28 #endmeeting