23:58:50 #startmeeting Ansible Azure Working Group 23:58:50 Meeting started Wed Jul 24 23:58:50 2019 UTC. 23:58:50 This meeting is logged and archived in a public location. 23:58:50 The chair is nitzmahone. Information about MeetBot at http://wiki.debian.org/MeetBot. 23:58:50 Useful Commands: #action #agreed #halp #info #idea #link #topic. 23:58:50 The meeting name has been set to 'ansible_azure_working_group' 23:59:11 yo 23:59:27 hello 00:00:04 #chair jborean93 yungezz zikalino826544 MyronFanQiu 00:00:04 Current chairs: MyronFanQiu jborean93 nitzmahone yungezz zikalino826544 00:00:25 I don’t have topic today. And thank you for Pr reviewing, will look at comments today 00:00:43 hello 00:00:56 i just want to ask about a few things regarding collections 00:01:02 Great- go ahead! 00:01:14 basically i wonder how should the collections handle documentation. 00:01:47 The plugin docs work exactly the same way- as far as publishing and online availability of the docs, the docs team is still working that part out 00:01:47 should it be generated manually, then published somewhere and link available via galaxy? or what's the idea? 00:02:20 I think the intent is that the docs will be generated by Galaxy from the collection artifacts and published automatically 00:02:26 (but that's not my direct area) 00:02:35 so it's possible that collection doc will be hosted on ansible website? 00:02:50 That's what I've heard 00:02:56 and also the tests, they should be collection owner responsibility? 00:03:16 Yes, we're working on the testing tools right now, and the tests will live inside the collection 00:03:42 mattclay is extending ansible-test to be able to run unit/integration tests on collections, and ansible-test will ship as part of Ansible itself in 2.9 00:04:28 so the tests inside the collection would use ansible ci, just like it's done now? 00:05:01 Yes, and moving the tests from Ansible to a collection will (in most cases) just be a matter of moving the directory 00:05:22 I would think that running the tests would be up to you but the actual tooling is the same 00:06:43 IIUC certified partners can choose to leave the CI with us or externalize it, but also not my area 00:06:53 ah ok 00:07:34 IIRC continuing to use our CI will require that the collection lives under the ansible/ github org still 00:08:46 Have you been able to get the installation stuff working? 00:10:00 yes, everything works fine :-) 00:10:06 Great! 00:10:32 perhaps introducing some prerecording of tests would be a good idea. 00:10:48 Once you're in a collection, you can do pretty much anything you like :D 00:11:15 I played with that awhile back using the stuff in the Azure SDK, but it seemed to be very brittle 00:11:32 Workable enough for testing the SDK itself, but not so good for what we needed 00:11:52 (plus adding the test deps would likely have caused us problems) 00:12:46 But if you can come up with a good way to abstract that and put the modules/SDK in "test mode" to trigger recorded responses, fantastic... 00:14:15 I played with a mock REST API for the inventory plugins, but never got it solid enough that I was comfortable committing it 00:14:38 well, i just work on azure cli now and python sdk, so i have new ideas... ;-) 00:15:02 Nice... :) 00:15:07 Anything else to discuss today? 00:16:24 If nothing else, will close in 1min... 00:17:10 i think i haev nothing else 00:17:15 thank you :-) 00:17:35 Cool- well, until next week then... Thanks all! 00:17:43 #endmeeting