20:00:03 #startmeeting Ansible Windows Working Group 20:00:04 Meeting started Tue Nov 6 20:00:03 2018 UTC. 20:00:04 This meeting is logged and archived in a public location. 20:00:04 The chair is nitzmahone. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:00:04 Useful Commands: #action #agreed #halp #info #idea #link #topic. 20:00:04 The meeting name has been set to 'ansible_windows_working_group' 20:00:11 #chair jborean93 20:00:11 Current chairs: jborean93 nitzmahone 20:00:19 hey 20:00:26 hey 20:00:54 Sounds like no Jon today; nothing new on the agenda 20:01:02 #topic open floor (mind the gap) 20:01:14 https://github.com/ansible/ansible/pull/46516 20:01:41 Bah, that's my bad, still need to review 20:02:43 when will be a code freeze for 2.8? 20:02:52 Probably end of January 20:02:58 https://github.com/ansible/ansible/pull/48051 20:03:27 I would like to make that script more enterprise friendly - with usage existing certificates 20:03:56 in the next commit I'll add bump a number to 2.0 because I would like to change parameters 20:04:34 I really don't want to add more functionality to that script 20:04:43 enterprises should be using their own version specific to their task 20:06:07 as I observe that it's a blocker for pilots 20:07:33 it's just there are already bad things being done in that script which we can't change 20:07:52 I don't want to add more surface area 20:09:10 maybe can we try release 2.x ? 20:09:16 with Ansible supporting http listeners there is less of an issue with adoption 20:10:53 there were plans to make this a PS module with more granular control but it never got off the ground 20:11:12 I like that idea! 20:11:17 I'd be much more inclined to support --^ than adding a bunch more stuff to what we have 20:11:36 and I can try to do that 20:11:42 The only reason it still lives where it does is because people run it directly from GH in their CI stuff, so making breaking changes to args is problematic 20:11:48 o/ 20:12:42 OK, so my proposal is 20:13:15 I will create the module to manage WinRM https listeners - partially based at the current script 20:15:23 and maybe in the future you will deprecate the ConfigureRemotingForAnsible.ps1 in favor to the module 20:15:41 world peace seems to be easier :( 20:16:23 At some point we'll probably need to rip off that bandaid, but I dunno what the best plan is there 20:17:15 I unfortunately don't see a module changing that, it's a lot easier to just download a script and execute than a proper module 20:20:03 Hi Matt, Jordan - late to the meeting. I use Ansible to config manage a few windows/server desktops, just wanted to login and "listen in" 20:20:12 hey 20:20:30 In the end I am -1 to making any changed to the configure script, especially features 20:20:48 OK, I understood 20:20:51 We need to come up with future plans and what that actually looks like 20:22:11 We should add a big warning at the top saying stop pulling directly from GH 20:22:30 and that it isn't the most secure/use at your own discretion 20:22:47 and we're gonna pull that rug out from under you at some point 20:23:23 should we also add an `Write-Warning` to say this will be removed/dramatically changed in the future? 20:23:28 "What, a Github file blob doesn't count as a highly available service?" ;) 20:23:35 OK by me 20:26:12 #48051 20:26:15 closed 20:26:25 Anything else for today? 20:26:35 nope 20:26:47 I'm good, need to get back onto reviewing some of these PRs this week 20:26:52 same 20:27:40 OK, closing in 5... 20:27:42 4.. 20:27:45 3.. 20:27:47 2.. 20:27:49 1.. 20:27:53 Thanks all- til next week! 20:27:56 #endmeeting