20:00:27 <jborean93> #startmeeting Ansible Windows Working Group
20:00:27 <zodbot> Meeting started Tue Nov 17 20:00:27 2020 UTC.
20:00:27 <zodbot> This meeting is logged and archived in a public location.
20:00:27 <zodbot> The chair is jborean93. Information about MeetBot at http://wiki.debian.org/MeetBot.
20:00:27 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
20:00:27 <zodbot> The meeting name has been set to 'ansible_windows_working_group'
20:00:34 <jborean93> #chair nitzmahone
20:00:34 <zodbot> Current chairs: jborean93 nitzmahone
20:00:36 <briantist> 🌊
20:00:44 <jborean93> hey
20:00:53 * nitzmahone lurks
20:01:34 <briantist> *skulks*
20:01:54 * jhawkesworth lurking
20:01:59 <jborean93> looks like just 1 thing on the agenda https://github.com/ansible/community/issues/517#issuecomment-726792514
20:02:07 <jborean93> really just a question to look at the issue
20:02:33 <jborean93> I will admit I've had a look at https://github.com/ansible-collections/ansible.windows/issues/18#issuecomment-707755873 but my brain wasn't ready to deal with it
20:03:00 <briantist> same, and I'd rather see it as a proper PR to review/comment
20:03:03 <jborean93> there's another win_acl issue which I haven't had the courage to look into
20:03:31 <briantist> link / issue #?
20:04:06 <jborean93> this is the other one https://github.com/ansible-collections/ansible.windows/issues/110
20:05:28 <briantist> looks like it'll take some time to dig into but it seems like a very complete writeup with ways to repro at least
20:06:23 <jborean93> yea there is a lot of information in there
20:07:30 <jborean93> I just know that one persons interpretation of the rules may not match another person's interpretation
20:07:48 <jborean93> or at least the whole canonicalisation of the rules is going to get quite hairy
20:09:42 <jhawkesworth> I guess it would be useful to know what rights the test user is running as has for that one.
20:10:03 <briantist> good point, ACLs are complicated and the bulk of the work decoding that issue will be around interpretation :-/
20:11:19 <jborean93> but just lamenting I need to look at 2 win_acl issues
20:11:25 <jborean93> thanks for commenting on the issue asking for a PR though
20:11:30 <jhawkesworth> It's not something I understand well but there's no all-seeing set of rights so that's going to make it hard
20:12:36 <jborean93> #topic open floor
20:12:46 <jborean93> anywho, that out of the way is there anything you wish to talk about
20:14:18 <briantist> I have nothing Windows related. I recently became the maintainer for the `hashi_vault` lookup in c.g and that's in the process of being split out to its own collection, so I'm kind of excited about that 😅
20:14:31 <jhawkesworth> If anyone knows someone who might be interested in taking on the win_xml, I think it is time for me to step back.
20:14:51 <jhawkesworth> I am not getting ansible time in my current role.
20:15:17 <jborean93> briantist: awesome, good luck with it all
20:15:28 <briantist> thanks!
20:15:42 <jborean93> jhawkesworth: I'm sure someone can step up if they wish, sad you can't work on Ansible as much but maybe some day in the future
20:17:10 <briantist> I'll keep my ears open jhawkesworth but I don't know of anyone just now
20:19:30 <jhawkesworth> Yeah, let's hope so. Thanks briantist . Sad I haven't managed to make ansible my day job, but that wasn't meant to be
20:20:25 * jhawkesworth adopts ansible Windows honcho emeritus status
20:20:29 <jborean93> one day you'll be back
20:21:28 <jhawkesworth> :-)
20:22:40 <jborean93> cool, anything else we wish to discuss
20:22:43 <jborean93> will close in 2 if now
20:22:55 <briantist> nothing from me
20:25:06 <jborean93> awesome
20:25:11 <jborean93> well I'll let you all get back to your days
20:25:14 <jborean93> have a good one all
20:25:16 <jborean93> #endmeeting