23:59:52 #startmeeting Ansible Azure Working Group 23:59:52 Meeting started Wed Mar 27 23:59:52 2019 UTC. 23:59:52 This meeting is logged and archived in a public location. 23:59:52 The chair is nitzmahone. Information about MeetBot at http://wiki.debian.org/MeetBot. 23:59:52 Useful Commands: #action #agreed #halp #info #idea #link #topic. 23:59:52 The meeting name has been set to 'ansible_azure_working_group' 00:00:10 #chair yungezz yuwei jborean93 00:00:10 Current chairs: jborean93 nitzmahone yungezz yuwei 00:00:29 hey 00:00:42 hi 00:00:45 I have 2 topics today, prs and facts/info thing 00:00:56 Hi Jordan 00:01:49 For prs, one of mine: https://github.com/ansible/ansible/pull/53161 00:02:32 Looks like it has a merge conflict 00:02:43 servicebus and workspace PR https://github.com/ansible/ansible/pull/53731  https://github.com/ansible/ansible/pull/51320 00:03:00 I will fix the conflict 00:03:25 Not sure does zim has Pr also 00:03:32 Let me check 00:05:38 hello :-) 00:05:54 good $time_in_your_region 00:06:15 Hi zim, do you have pending review prs? 00:07:03 just these i mentioned from 3rd party contributor 00:07:22 https://github.com/ansible/ansible/pull/53622 00:07:37 he mentioned he will merge my changes into his a day ago 00:07:42 but i think still not there 00:08:00 community freeze is next week, so still some time 00:08:27 I've got a PR that will need to be reviewed by you before it's merged 00:08:27 https://github.com/ansible/ansible/pull/54443 00:09:01 The requirements file has conflicting versions and this upgrades 3 of them so the `msrestazure` has a valid version 00:09:15 Unfortunately I've had to make changes to the modules but hopefully I've picked up most of them 00:09:19 yuwei: servicebus changes look good, fix merge conflict then good to merge 00:09:24 for me looks good, are ll the latest? 00:09:51 jborean93 i will check the details and merge 00:10:14 `azure-mgmt-batch` is not the latest as it was 2 major versions behind and I didn't want to make any big leaps 00:10:18 thanks 00:10:25 Yeah, not sure how we can keep that from happening in the future 00:10:43 i was also planning to look into versions before freeze so i think you did most of the work :-) 00:10:46 Other than maybe pip install the requirements file to a fresh venv and watch for errors 00:10:52 Will be looking at making sure we test the requirements file for these conflicts 00:11:00 i will upgrade later if anything is still behind 00:11:05 sounds good 00:11:29 IIRC there were a few that were still using prerelease versions because we'd have to significantly update the modules for the post-release versions 00:11:38 I don't know if `azure-mgmt-web` has a bug but it no longer raises `CloudError` if a resource does not exist, couldn't find any docs on this 00:11:49 But I'm guessing we're going to run into this kind of thing more and more for the ones that are lagging behind. 00:15:37 Any other Pr? If no more prs, then facts/info thing 00:15:51 nothing from me 00:18:36 a kind of silent :-) so that facts/info thing... 00:18:47 For facts to info renaming, we don’t want to change it in 2.8 as listed in the Pr, but some of new modules was merged by Bcoca already. We’d like to revert this to avoid inconsistency to users 00:18:55 agreed 00:19:13 on reverting? 00:19:22 Matt could you help to talk with bcoca on the history why we removed ansible_facts? 00:19:26 yeah, fine with me to keep consistency for 2.8 00:19:58 I think we need get his approval to do reverting right? 00:19:59 Yes, I'll make sure there's no hassle from this end 00:20:00 well, bcoca seems to not agree, just a bit worried 00:20:20 Thanks Matt! 00:20:20 and i still have 5 modules to merge 00:21:07 We've had this pattern for a long time in the absence of a non-_info suffix, so no reason to change it until 2.9 when we have something agreed-upon to change it to 00:21:07 So when every thing ok, pls help to approve the reverting Pr 00:21:08 will there be any special announcements about _info in the future? 00:21:36 Yeah, we'll update the developer guide and probably add some automated checks for new modules that ensure _facts only return _facts and that _info does not 00:21:38 i think that's what's very important for us. 00:22:00 That will be great, update developer guides 00:22:06 i think i like "that ensure _facts only return _facts and that _info does not" very much 00:22:08 it was only recently decided to use `_info` for "facts" modules that don't return `ansible_facts`, so tests and docs should be forthcoming 00:22:34 It's been floating around as an idea for awhile, but we recently decided for sure that's the plan 00:22:55 (and as part of 2.9 will figure out whatever the transition process looks like w/ aliases etc) 00:23:04 Got it. So we little confused at beginning 00:23:39 Which could possibly include even dynamically masking ansible_facts returns if an _info module returns them (we know how it was called, so the aliased ones would probably just work) 00:23:47 while talking about naming..... 00:24:05 shoud we decide on usage of _underscores_ in the middle of module names? 00:24:14 Yeah, sorry about that- I think I was pretty clear that we should hold off doing anything until 2.9, but sounds like not everyone else on the Ansible side was on the same page 00:24:35 We could 00:24:40 Ok, thank you Matt 00:25:29 So would you want to do underscores everywhere? 00:25:50 (if we had the corporate DeLorean and could go back in time to change it?) 00:26:04 yes, yuwei already started adding _ in some modules, but i am not sure yet 00:26:05 :) 00:26:22 we have some inconsistencies 00:26:26 * nitzmahone looks through current modules for "the worst offender" if we did it that way 00:26:43 for instance 00:26:50 azure_rm_virtualmachine_extension 00:26:54 azure_rm_application_security_group_facts 00:27:03 and azure_rm_virtualmachineextension_facts 00:27:13 i created _facts to match other modules 00:27:27 but it doesn't match azure_rm_virtualmachine_extension 00:27:44 i was thinking of renaming azure_rm_virtualmachine_extension to match 00:28:19 We can remove extra underscore 00:28:27 To keep consistency 00:28:32 If we want to stay consistent with the majority, it should be azure_rm_(thingymabobwithnounderscoresanywhere)(_facts|_info)? 00:28:41 Agree 00:28:49 yes, that's what i want to do. to test rname/obsolete process 00:29:00 OK 00:29:26 so do you think we should also change **azure_rm_aks_version** 00:29:29 So don't do it yet, since we don't know exactly what we're going to do there yet, but once we figure it out, including that one in the pile should be fine 00:29:49 it's inconsistent, so probably 00:29:50 so I need to change the servicebus one 00:29:56 you mean about nunderscores or renaming? 00:30:21 and i think azure_rm_aks_version is also facts, so it should be azure_rm_aksversion_facts 00:30:28 Underscore for service bus 00:31:23 like azure_rm_servicebusqueue 00:31:29 yeah 00:32:00 If we're going to clean the others up to no underscores except main Azure prefix and _fact/_info, they probably should be renamed before we merge them 00:32:10 (servicebus) 00:32:18 Yes 00:32:52 ok, good, one more consistency issue settled down. makes me happy :-) 00:33:40 No more topic from me 00:34:00 Cool, nothing else here either. Thanks all! 00:34:03 closing in 5.. 00:34:06 4.. 00:34:09 3.. 00:34:12 2.. 00:34:15 1.. 00:34:17 Thanks everyone! 00:34:18 #endmeeting