20:00:36 <jborean93> #startmeeting Ansible Windows Working Group
20:00:36 <zodbot> Meeting started Tue Feb 11 20:00:36 2020 UTC.
20:00:36 <zodbot> This meeting is logged and archived in a public location.
20:00:36 <zodbot> The chair is jborean93. Information about MeetBot at http://wiki.debian.org/MeetBot.
20:00:36 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
20:00:36 <zodbot> The meeting name has been set to 'ansible_windows_working_group'
20:00:40 <jhawkesworth> hey
20:00:45 <jborean93> howdy
20:00:50 <jborean93> #chair jhawkesworth
20:00:50 <zodbot> Current chairs: jborean93 jhawkesworth
20:01:00 <jborean93> just me today, Matt is having some lunch
20:01:07 <jhawkesworth> ok
20:01:24 <jborean93> I'll give it 1 more minute to see if anyone else joins
20:01:28 <jhawkesworth> anyone else joining in with Windows Working Group today?
20:01:55 <rainmatter> jborean93: thank you!
20:03:00 <jborean93> I think it might be just us
20:03:05 <jhawkesworth> fair enough.
20:03:11 <jborean93> did you want to talk about the meeting time change?
20:04:26 <jhawkesworth> yeah, but I know this time is best available for you, and works for nitzmahone so unless anyone else says 'hey it needs to change' I guess we can leave things as they are
20:05:17 <jhawkesworth> no comments on the agenda on that either so I think let's move on.
20:05:19 <jborean93> I'm open to changing it, this is really just the earliest I can do (for maybe the last 9 hours)
20:05:46 <jhawkesworth> understood.
20:05:59 <jborean93> I think with the small number of people turning up there really isn't too much that gets discussed here
20:06:14 <jborean93> it would be nice to go back to the turnout we were getting a year ago or so
20:06:18 <jhawkesworth> my kids are getting bigger so later bedtime these days and its starting to clash, but with daylight saving change coming up it will be ok
20:06:24 <jhawkesworth> indeed.
20:07:40 <jhawkesworth> well noone else is chipping in about meeting time or frequency and as you say not much getting discussed at the moment I guess we should move on
20:07:41 <jborean93> Once the move to collections is done and dusted it might be time to re-evaluate how we hold these meetings but that won't be for another 2 or 3 months probably
20:07:46 <jborean93> cool
20:07:51 <jborean93> #topic https://github.com/ansible/community/issues/517#issuecomment-584820172 warn action
20:08:19 <jhawkesworth> yeah I wasn't aware you could turn off warnings at all until I saw this one.
20:08:27 <jborean93> I have yet to actually look at the issue thoroughly but `warn: no` is not common to modules
20:08:39 <jhawkesworth> only ref I've found so far seemed to be for command/shell
20:08:49 <jborean93> It's something that is implemented only on command/shell https://docs.ansible.com/ansible/latest/modules/command_module.html
20:09:23 <jborean93> yep, even the `args:\n...` way of writting is how to specify extra options for modules like command/shell that use the raw yaml value like `- command: value`
20:10:12 <jhawkesworth> ok, so https://github.com/ansible/ansible/issues/66804 is a feature request really
20:10:44 <jborean93> pretty much and honestly it's not really something we probably would implement per module
20:10:52 <jborean93> it should be a generic task attribute or something
20:11:14 <jborean93> https://docs.ansible.com/ansible/latest/reference_appendices/config.html#action-warnings can toggle all warnings on and off, unfortunately it doesn't look like it is configurable as a variable so it must be set before running Ansible
20:11:29 <jhawkesworth> given its at action level it would be horrible to have per module.
20:12:29 <jhawkesworth> the warn stuff in win_xml is really useful when you are trying to get it set up right.  Maybe there's a better way of getting it to output the warnings.
20:12:45 <jborean93> is the warning actually valid, maybe the module is warning too much
20:13:42 <jhawkesworth> I think there are some valid warnings along the lines of 'I tried to match the xpath you specified but found nothing that matched' but others are probably overkill once you have got the manipulations correctly configured.
20:14:02 <jhawkesworth> I find xpath fiddly myself so expect to get it wrong a few times
20:14:21 <jborean93> If you have an XPath and it was invalid/not found I would assume that should error out. Do you know how the xml module handles that behaviour
20:15:04 <jhawkesworth> well I'm going to take the lid off it anyway to dig into https://github.com/ansible/ansible/pull/66081/files so I'll have another look
20:15:18 <jhawkesworth> iirc it just warns if the xpath was not found.
20:15:48 * jborean93 personally just wants to stay away from the tire fire that is xml
20:16:05 <jhawkesworth> yeah totally.
20:16:27 <jhawkesworth> its an occupational hazard when day job involves maintain soap web services (still!)
20:17:01 <jborean93> but from a brief look outside it seem like the warnings should potentially be errors or warnings that shouldn't be warnings. It's hard to tell though without actually using the module
20:17:21 <jhawkesworth> thanks, I think I have a plan then.  I will have a look and see if the warnings can be rationalized a bit.
20:17:34 <jborean93> But what the user wants is really a feature request and not really something we should be implementing per module. There should be a way to disable warnings per task
20:18:34 <jhawkesworth> yeah, there was a feature request for that long ago https://github.com/ansible/ansible/issues/13468 but scope was not generic
20:19:54 <jhawkesworth> ok, unless anyone else has anything to add about win_xml warn: no I think I'm done on that topic
20:19:55 <jborean93> is there anything else you wanted to discuss on that one?
20:20:00 <jborean93> awesome
20:20:03 <jborean93> #topic open floor
20:20:09 <jborean93> anything else you wanted to talk about today?
20:20:21 <jhawkesworth> no I'm good
20:20:51 <jhawkesworth> thanks for squashing all those old bug reports btw!
20:21:01 <jborean93> I'm currently working on a windows service module util that exposes some of the more obscure Windows service configurations. Should hopefully have a `win_service_info` module by the end of the week and then win_service is next
20:21:10 <jborean93> There's still plenty to go but it's a start
20:21:15 <jhawkesworth> nice.
20:21:38 <jhawkesworth> busy setting ansible-lint to work on all my 200 roles and 300 playbooks.  Lots to fix!
20:22:04 <jhawkesworth> may get an hg_info module out of that though as hg module doesn't do a lot of what I need
20:22:41 <jhawkesworth> sorry I'm going to have to drop, catch you next time
20:22:42 <jborean93> always fun turning on linting to see what needs to be fixed
20:22:49 <jborean93> the ansible-test ignore file just keeps on getting larger and larger
20:23:20 * jhawkesworth afk -srry
20:23:36 <jborean93> no worries, have a good one
20:23:39 <jborean93> #endmeeting