ansible_windows_working_group
LOGS
20:00:16 <jborean93> #startmeeting Ansible Windows Working Group
20:00:16 <zodbot> Meeting started Tue Sep 17 20:00:16 2019 UTC.
20:00:16 <zodbot> This meeting is logged and archived in a public location.
20:00:16 <zodbot> The chair is jborean93. Information about MeetBot at http://wiki.debian.org/MeetBot.
20:00:16 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
20:00:16 <zodbot> The meeting name has been set to 'ansible_windows_working_group'
20:00:32 <jborean93> ahoy-hoy
20:00:34 <jtanner> hello.exe
20:01:54 * jborean93 listening to the crickets
20:04:47 <jtanner> so, yeah ... windows ...
20:04:57 <jborean93> are you starting to work on it now :)
20:05:03 <jtanner> no
20:05:07 <jtanner> only when there's a firedrill
20:05:44 <jtanner> i assume at some point i'll have to figure out how slow pywinrm is for 1K hosts/forks
20:06:04 <jborean93> I think you only need 1 guess for that
20:06:19 <jtanner> =(
20:06:32 <jtanner> my guess is spelled p.a.i.n.
20:07:03 <nitzmahone> sorry, ignored my alarm and kept poking at a bug
20:07:12 <nitzmahone> Looks like I missed a lot ;)
20:07:18 <jborean93> so much
20:07:38 <jtanner> we fixed all the bugs, you can retire from windows now
20:07:47 <nitzmahone> sweet, c'ya
20:07:50 <nitzmahone> ;)
20:07:59 * nitzmahone wrote many of them
20:08:16 <jtanner> yeah, we deleted all your lines in git blame and the bugs vanished
20:08:23 <nitzmahone> sweet
20:09:00 <jborean93> does that mean no windows code at all?
20:09:06 <nitzmahone> burn it all down
20:09:41 <nitzmahone> Theoretically if we successfully extract the Windows exec subsystem into a plugin, it could all live in a collection
20:09:50 <jtanner> you folks doing a windows breakout on monday?
20:10:16 <nitzmahone> I hadn't planned on one ATM
20:10:48 <jborean93> same, if there are people there for Windows then I'm sure we can still sit down
20:10:50 <nitzmahone> I don't think there's a lot to discuss ATM
20:11:49 <nitzmahone> We had a rather impromptu session last time that was mostly a video version of a WWG meeting, including some PR review and other randomness
20:12:34 <jtanner> speaking of collections ...
20:12:52 <jtanner> either of you played around with powershell based modules inside collections?
20:12:54 <nitzmahone> <.<
20:13:05 <jborean93> yep, nitzmahone wrote tests for that
20:13:07 <nitzmahone> Yeah, there are integration tests that do it
20:13:52 <jborean93> https://github.com/ansible/ansible/tree/devel/test/integration/targets/collections/collection_root_user/ansible_collections/testns/testcoll/plugins
20:14:04 <jborean93> modules, ps utils, and c# utils
20:14:34 <nitzmahone> Did you end up merging the "less magic" tweaks to the Requires syntax?
20:14:38 <jborean93> yep
20:14:41 <nitzmahone> cool
20:14:53 <jborean93> just need to add relative support for 2.10 :)
20:15:19 <jtanner> iirc relative and subdirs were tied together ...
20:15:26 <nitzmahone> *theoretically* shouldn't be too hard, but the devil's in the details, I'm sure
20:15:30 <jtanner> does that imply ps modules can't live in colleciton subdirs?
20:15:39 <nitzmahone> He means specifically for PS imports
20:15:41 <jborean93> they can after that change to the requires statement
20:16:12 <jborean93> https://github.com/ansible/ansible/pull/61307 to be specific
20:16:57 <jborean93> how tf was that 21 days ago
20:17:05 <jtanner> welcome to ansible
20:17:42 <jtanner> feels like last week that i demo'ed folecule and collections hacks
20:17:46 <nitzmahone> I have that experience both ways, like "holy crap where did September go?", but also some things like "that was only 2 weeks ago? Feels like years."
20:18:58 <jborean93> I think 2.8 gave me a false sense of the release timeframe. It was a lot longer than usual and 2.9 was like bam freeze
20:20:52 <jborean93> anywho I don't think there's anything else we want to talk about so lets get on with our days
20:21:48 <jborean93> #endmeeting