20:00:58 #startmeeting Ansible Windows Working Group 20:00:58 Meeting started Tue Feb 12 20:00:58 2019 UTC. 20:00:58 This meeting is logged and archived in a public location. 20:00:58 The chair is nitzmahone. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:00:58 Useful Commands: #action #agreed #halp #info #idea #link #topic. 20:00:58 The meeting name has been set to 'ansible_windows_working_group' 20:01:10 hi 20:01:18 hey 20:01:26 @nitzmahone: ill ask after the meeting. have thoughts on what you just said 20:01:47 #chair it-praktyk[m] jhawkesworth_ 20:01:47 Current chairs: it-praktyk[m] jhawkesworth_ nitzmahone 20:02:08 you guys and your special-characters-included nicks make me crazy ;) 20:02:28 #info agenda: https://github.com/ansible/community/issues/420 20:02:44 irccloud 'gave' me the _ and I'm too lazy to get rid of it 20:03:20 I think Jordan's out this morning, so I guess let's just get started 20:03:38 it's a power efficiency not laziness ;) 20:03:58 there, gone 20:04:15 laziness is a programmer virtue 20:04:16 * nitzmahone won't really start complaining until non-printing chars and high unicode chars start showing up ;) 20:04:19 anyway 20:04:36 are we starting here: https://github.com/ansible/community/issues/420#issuecomment-462125577 ? 20:04:45 #topic * https://github.com/ansible/ansible/pull/50033 20:04:50 (backup arg on modules) 20:05:46 ok 20:05:53 * jhawkesworth catching up 20:06:06 Hey I will be in and out, just on my mobile for now 20:06:08 I'm +1 for merge at this point; it's passing tests and I think all the current feedback has been incorporated 20:06:20 #chair jborean93 jhawkesworth 20:06:20 Current chairs: it-praktyk[m] jborean93 jhawkesworth jhawkesworth_ nitzmahone 20:06:31 Anybody else have objections? 20:06:52 +1 20:07:03 no objections. 20:07:15 the only objection I still have is the win_copy behaviour around backup 20:07:24 I believe dag said he was going to investigate 20:08:00 jborean93: this? https://github.com/ansible/ansible/pull/50033/commits/15ee38f447658d57c6f9ca9412e8f0b4808bde21 20:08:42 unless I've missed something win_copy got fixed 20:08:57 yep, there was an outstanding question around how that works with the 3 different win_copy modes, control -> remote (single file), control -> remote (multi file), remote -> remote (any) 20:09:05 ah yeah I see it now 20:09:16 I believe it works for everything except the middle one and dag was going to see how copy operated 20:09:34 i only tried single file 20:10:16 I looked at multi-file a bit ago and it looked like it would do the right thing, but I didn't actually try it 20:10:23 for the testing side I can follow up on making it a bit more efficient and fix the localisation requirements, dag's done enough 20:10:26 (as I had a similar question) 20:10:40 OK- I'll make that note on the PR 20:10:49 AFAIK multi file just "explodes" from the zip and doesn't use the methods he's current;y changed 20:11:53 * jborean93 back at my desk 20:12:09 https://github.com/ansible/ansible/pull/49701 20:13:10 we went through that and said it can't be looked at until pywinrm has been updated 20:13:23 yeah, was gonna say that doesn't look quite right 20:13:23 same with * [25532](https://github.com/ansible/ansible/issues/25532) 20:14:00 and at that point pywinrm was thought to be mostly dead in the water feature wise 20:14:12 https://github.com/ansible/ansible/pull/45870 20:14:46 just needs validation, I think jhawkesworth was going to test it out 20:14:58 * jborean93 looks he has already :) 20:14:58 he did everything but hyper-v 20:15:30 yea I can try and test out a hyper-v host today or tomorrow 20:15:52 I have hyper-v installed but so far not managed to get any vms running in it 20:16:11 you can use Vagrant to set one up easily 20:17:27 not sure if this is still the case but it used to be you could either run hyper-V or virtualbox virtualisation but not both on the same box. 20:17:41 I don't think we're going to do the upstream releases necessary for https://github.com/ansible/ansible/issues/25532 right now 20:17:55 yea that's the same as the read_timeout PR 20:18:14 psrp has it included though so there's some avenue to set that 20:18:19 that's fair enough 20:18:23 https://github.com/ansible/ansible/pull/50759 20:19:01 it's related to the point that to agenda that I asked 20:19:12 I not a big fan of updating dependencies in the background but it seemed like we did that in the test so it's not a change 20:19:16 updating PackageManagement and PowerShellGet 20:19:33 really a question as to whether we do it or get the user to, it doesn't seem that bad though so I'm ok with the PR 20:19:43 What do you think about adding an additional switch 20:20:00 updating that dependencies is necessary 20:20:21 I think that's probably a bit too much, considering the simplicity of updating the dep right now I'm ok with it, it's just not ideal 20:20:35 but MS would have no needed an updated dep in an ideal world 20:20:58 World is not ideal 20:21:03 I think we can implement a tinfoil-hat mode in the future if people request it, but I'm OK with it as-is 20:21:36 yea, +1 to me. A user cna always update before if this step fails at least we try and make it easier for users 20:22:11 OK, merging 20:22:24 thx 20:22:34 nice 20:23:17 https://github.com/ansible/ansible/pull/50808 20:23:32 hrm, are those our S3 buckets? 20:23:42 yep I uploaded them 20:23:45 yes 20:24:04 +1 for this then as well 20:24:12 seems to have conflicts now 20:24:24 perhaps due to merge just done 20:24:43 yeah, probably- if you want to fix those it-praktyk[m] we can get it merged 20:24:52 I'll update that 20:24:58 I'm in favour of having this 20:25:23 I'll do that :) 20:25:30 thanks! 20:25:45 #topic: win_format idempotency 20:26:07 chopraaa? 20:26:20 hey 20:26:22 did we talk about this last week and forgot to update the agenda? 20:26:36 yeah we talked about this - plus i didnt really get around to it 20:26:39 busy week 20:26:55 no worries, did you get what you wanted from last week or is there more you want to talk about? 20:27:04 yep 20:27:46 decided to format where it was detected to be safe - otherwise require a force param 20:28:02 ok, cool 20:28:04 #topic https://github.com/ansible/ansible/pull/51986 20:28:10 safe as in unformatted partitions 20:28:32 I'm ok with supporting checksums, not sure if we want to follow the same module options as get_url 20:28:43 never liked the algo:hash format but that's just me 20:29:20 you'd rather discrete subdict or ? 20:29:59 either that or 2 options like we do with win_stat 20:30:10 but now that would be going against what get_url does 20:30:26 Apart from that I haven't actually gone to review the code 20:30:35 wow, big changes 20:30:37 so I want the feature but I haven't really looked at it too much 20:30:42 yea that's a bit worrying 20:31:52 k, not gonna code review this live- anyone else have an opinion on the checksum UI support for win_get_url? 20:32:25 nice to have. I suspect path of least resistance is to keep ui same as get_url for now... 20:32:36 my vote is `checksum_algorithm` and `checksum` as 2 options but I'm not married to it 20:32:44 ... although I prefer the stat/win_stat way, that could be different 20:33:27 i guess it wasn't there before, might as well have `checksum_algorithm` and `checksum` 20:33:37 which just leaves get_url as outlier 20:33:56 +1 to discrete args- if anyone complains loudly we can add support for the algo:sum to checksum later 20:33:57 could be retrofitted there and deprecated over time 20:34:13 yep, I just hate splitting values and then validating 20:34:28 makes ugly module code for sure! 20:34:28 if we have discrete args we can build the checks in the module arg spec for cleaner documentation 20:35:19 yep, worth asking for as part of this PR then I think 20:35:36 OK, will comment as such, though it also feels like the impl is overwrought at first glance 20:37:46 is this a similar thing to the Nuget provider update https://github.com/ansible/ansible/pull/50621#discussion_r249645345 ? 20:38:18 that exactly the same case 20:40:52 so on that specific question, same answer I guess- default to updating what's necessary and implement a "paranoid" switch later that skips the updates and fails instead if people want it 20:41:20 #topic open floor 20:41:23 I'm OK with that 20:41:46 NuGet was previously updated - since the initial version of the win_psmodule 20:42:36 Anything else burning for today? 20:43:10 not from me 20:43:21 https://github.com/ansible/ansible/pull/50808 - rebased, will be ready for merge after CI tests 20:44:35 cool, should auto-merge after tests pass 20:45:00 OK, if nothing else, closing in 5.. 20:45:03 4.. 20:45:06 3.. 20:45:09 2.. 20:45:10 1.. 20:45:13 let nitzmahone get his lunch 20:45:15 Thanks all- until next week! 20:45:23 thanks 20:45:25 thx 20:45:31 jhawkesworth: ;) 20:45:33 #endmeeting