20:00:51 <nitzmahone> #startmeeting Ansible Windows Working Group 20:00:51 <zodbot> Meeting started Tue Nov 5 20:00:51 2019 UTC. 20:00:51 <zodbot> This meeting is logged and archived in a public location. 20:00:51 <zodbot> The chair is nitzmahone. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:00:51 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic. 20:00:51 <zodbot> The meeting name has been set to 'ansible_windows_working_group' 20:01:00 <nitzmahone> #chair jborean93 20:01:00 <zodbot> Current chairs: jborean93 nitzmahone 20:01:08 <nitzmahone> #chair jhawkesworth 20:01:08 <zodbot> Current chairs: jborean93 jhawkesworth nitzmahone 20:01:55 * jhawkesworth lurking / mobile this evening 20:02:27 <jborean93> yo 20:02:34 <jborean93> anything we want to discuss 20:02:40 <nitzmahone> #info https://github.com/ansible/community/issues/420 20:03:16 <nitzmahone> I see https://github.com/ansible/ansible/pull/63968 - not sure if that's fixing a bug, or what 20:03:16 <jborean93> I see there's 3 at the bottom, 1 new module, 1 new feature, and another bugfix 20:03:42 <jborean93> I think it's fixing a bug, I thought it was fixed before but will have to double check 20:03:50 <jborean93> talking about https://github.com/ansible/ansible/pull/63414 20:04:31 <jborean93> I'm also apprehensive of adding this one, maybe if there was a way to hash/encrypt the credentials or something I would be ok with doing that 20:06:04 <nitzmahone> Yeah, I know there's a way to do it, just not sure what they're doing to create the LSA secret: https://blogs.technet.microsoft.com/doxley/2009/04/22/safely-setting-autologon-for-windows/ 20:06:17 <nitzmahone> ah: https://docs.microsoft.com/en-us/windows/win32/secauthn/protecting-the-automatic-logon-password?redirectedfrom=MSDN 20:07:08 <jborean93> fun more PInvoking, but that would add the functionality I would like to see in the module, compared ot just a user editing the keys themselves 20:07:30 <nitzmahone> And at that point the module's providing a lot more value-add 20:07:35 <jborean93> yep 20:07:38 <nitzmahone> (yes, I said it ;) ) 20:07:53 * nitzmahone commented as such on that one 20:08:14 <jborean93> cool 20:08:16 <nitzmahone> #topic open floor 20:08:34 <jborean93> I've given up for now on my little side project so I'm going to try and focus on reviews and Ansible PRs for the rest of the week 20:09:29 <nitzmahone> I see pywinrm did a 0.4.0 and a quick 0.4.1 to fix some bugs with the embedded requests_kerberos 20:10:07 <jborean93> yep, I've been running the beta for the past few days without any issues. Then again I haven't played too much in the winrm space the past few days 20:12:05 <nitzmahone> Well, anything else to kick around today, or shall we call it? 20:12:37 <mhunsber> can we talk about https://github.com/ansible/ansible/pull/56475? 20:14:15 <nitzmahone> go ahead 20:15:04 <mhunsber> last I heard, there was the 2.9 freeze so, but now you're on 2.10, right? 20:16:09 <jborean93> yea the freeze was just at the time of the last comment 20:16:13 <nitzmahone> Correct. The decision on whether we're allowing *any* new modules to be merged for 2.10 is still up in the air AFAIK (that's what should be nailed in the next few weeks) 20:16:46 <nitzmahone> Since we're likely pushing most everything out to collections during 2.10. 20:16:56 <mhunsber> oh okay. so more for the collections. thanks. 20:17:08 <nitzmahone> If we *don't* do that, then it's a good candidate for merging in 2.10 if people are thumbs-up for it 20:17:48 <jborean93> yep if we get the green light there I'm happy to merge this one 20:18:22 <nitzmahone> There was initially some talk of slow-rolling just new stuff into a few community collections that we'd ship in the box or make easily installable during 2.10, but it seems like we're moving more toward the "pull everything out during 2.10" 20:18:37 <nitzmahone> So we're holding off new module merges until that's finalized 20:21:19 <nitzmahone> Anything else for today? Going once... 20:21:28 <mhunsber> okay. I'll keep plugging my own PRs: https://github.com/ansible/ansible/pull/56033 this one isn't a new module, but adds tests for the iis application module. Should I just wait for the windows community collection for that one as well? 20:21:37 <jhawkesworth> Nothing from me 20:22:00 <mhunsber> it's also pretty old 20:23:07 <nitzmahone> At a glance 56033 looks OK- I'll restart CI on it to see if it's still happy 20:24:18 <nitzmahone> There's also still a very small chance that 2.10 will be 3.0, but I think that's less likely now 20:24:34 <nitzmahone> (which would potentially be a problem for the "version_added" field on that one) 20:25:38 <nitzmahone> Anything else going twice... :) 20:25:54 <mhunsber> that's it for me 20:26:07 <nitzmahone> Cool- thanks all! Until next week... 20:26:10 <nitzmahone> #endmeeting