00:00:02 #startmeeting Ansible Azure Working Group 00:00:02 Meeting started Thu Jul 18 00:00:02 2019 UTC. 00:00:02 This meeting is logged and archived in a public location. 00:00:02 The chair is nitzmahone. Information about MeetBot at http://wiki.debian.org/MeetBot. 00:00:02 Useful Commands: #action #agreed #halp #info #idea #link #topic. 00:00:02 The meeting name has been set to 'ansible_azure_working_group' 00:00:07 hey all 00:00:19 Hi Matt 00:00:19 #chair yungezz MyronFanQiu 00:00:19 Current chairs: MyronFanQiu nitzmahone yungezz 00:00:33 I don’t have special topic besides prs 00:00:42 Jordan's running an errand, so he won't be joining today 00:00:48 I have send out Pr lists 00:00:49 Ok 00:00:51 Yeah, got the list- thanks! 00:00:58 I'll look those over 00:01:10 hello everyone :-) 00:01:15 Thanks Matt 00:01:18 Hi zim 00:01:28 Hey Zim- were you able to publish a collection to Galaxy after Chris fixed the case on the namespace? 00:01:39 #chair zikalino826544 00:01:39 Current chairs: MyronFanQiu nitzmahone yungezz zikalino826544 00:02:32 we will try today again 00:02:54 yes, that namespace was a bit annoying :-) 00:02:55 great- let us know if you have any trouble. Are you using mazer or `ansible-galaxy collection build/publish`? 00:03:11 you could install roles with Azure.xxx or azure.xxx 00:03:41 and then if somebody made mistake and installed them with Azure.xxxx they had to refer to them with uppercase in playbooks too 00:03:42 Yeah, because collections are based on Python packages under the covers, the casing is very strict (unlike roles) 00:04:26 I'm still not 100% sure how Galaxy folks plan to handle incorrectly-cased namespaces in general 00:05:51 Also, relative import support will likely land in Ansible 2.9, so the Python imports for collection module_utils can be a lot shorter 00:07:05 (eg `from ..module_utils.azure_rm_common import blah` instead of `from ansible_collections.azure.rm.plugins.module_utils.azure_rm_common import blah`) 00:08:02 ok, so module can decide where to import module_utils from, right? 00:08:24 Correct, but you probably want to put the Azure module_utils in the collection rather than rely on what's in core 00:09:54 that's good feature, every collection can have their own version, which i believe was not possible with roles. 00:10:29 Another thing to consider with the collections move: `pip install ansible[azure]` will not do the right thing for collection-hosted anymore, since it will almost always be newer... 00:11:57 So Zim's new pattern that goes directly to msrestazure should make those modules much more stable. Ansible doesn't provide a mechanism for collection-hosted stuff to define Python requirements, so probably embedding a requirements file in the collection and documenting how to pip install would be good. 00:12:35 (similar to the current requirements file in packaging/requirements/requirements_azure.txt) 00:13:04 so, actually the only way to install collection is using mazer, right? 00:13:20 `ansible-galaxy collection build/publish` works in devel/2.9 00:13:28 sorry, `install` 00:13:31 (as well) 00:13:45 what would be typical from user's perspective? 00:13:48 build/publish/install are all working in devel 00:13:56 ansible-galaxy will be the final tool 00:14:16 mazer was experimental but I think it's done now 00:15:07 So please try with the ansible-galaxy tool, and let us know if you run into issues there 00:15:21 ok 00:16:06 Nothing else from me for today- anyone else? 00:16:23 No 00:16:35 OK, if nothing else, we'll close in 5.. 00:16:40 4.. 00:16:43 3.. 00:16:47 2.. 00:16:49 1.. 00:16:56 Thanks all- until next week! 00:16:59 #endmeeting