15:08:19 <bcoca> #startmeeting ansible core plublic irc meeting 15:08:19 <zodbot> Meeting started Thu Apr 9 15:08:19 2020 UTC. 15:08:19 <zodbot> This meeting is logged and archived in a public location. 15:08:19 <zodbot> The chair is bcoca. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:08:19 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:08:19 <zodbot> The meeting name has been set to 'ansible_core_plublic_irc_meeting' 15:08:32 <bcoca> #topic https://github.com/ansible/ansible/pull/68288 15:09:07 <bcoca> no one? 15:09:24 <DaazKu> Me 15:09:28 <jtanner> me ... 15:10:13 <bcoca> +1 from me, been wanting a 'non dependencies' requiresments for roles for long time, ony issue is now we have 'dual requirements.yml' that handles roles AND collections 15:10:58 <bcoca> i would standarize on that format from now on 15:11:18 <bcoca> but also, not make this a runtime issue, this should be 'on install' 15:11:46 <bcoca> whichi s what i belive the PR does , but the docs seem to hint otherwise 15:11:53 <DaazKu> The current implementation only works on install yes. 15:12:35 <bcoca> `Dependencies installed that way, depending on other factors described below, will also be executed **before** this role is executed during play execution.` or im just misreading this 15:12:38 <DaazKu> I tried my best do update the documentation to reflect that meta/requirements.yml are only on install and put that as the first point above meta/main.yml explanations 15:12:47 <DaazKu> This if for meta/main.yml 15:13:01 <DaazKu> https://github.com/ansible/ansible/pull/68288/files#diff-65f23e36b55ff5dbaa5e425562e97703R371 15:13:05 <bcoca> but that would be another instance of 'dependencies' .. i would rather have it INSTALL ONLY, no efect on runtime 15:13:06 <jtanner> i think the test should go into a new target dir 15:13:08 <DaazKu> vs https://github.com/ansible/ansible/pull/68288/files#diff-65f23e36b55ff5dbaa5e425562e97703R378 15:14:22 <DaazKu> bcoca the updated doc explain how to use meta/requirements.yml which only install dependencies and have no effect on runtime. 15:14:34 <DaazKu> I did keep the old documentation about meta/main.yml 15:15:01 <bcoca> k, that works for me, pending full review 15:15:05 <DaazKu> jtanner Why? 15:15:13 <jtanner> it's a new usecase 15:15:23 <jtanner> we shouldn't overload a test target with multiple usecases 15:15:26 <bcoca> jtanner: we normally have many use cases per target 15:15:35 <jtanner> we do, but that doens't make it right 15:15:40 <bcoca> the targets are per 'module/plugin/utility' 15:15:57 <jtanner> in some cases, but not always 15:16:00 <bcoca> making targets == use case breaks current pattern 15:16:08 <cyberpear> I assume this has the same format as any other requirements.yml? 15:16:10 <jtanner> it's not a consistent pattern 15:16:17 <DaazKu> cyberpear yes 15:16:27 <bcoca> jtanner: agreed, but i thought we were working to consolidate it, not break it more 15:16:35 * cyberpear has been creating such files in roles for some time 15:16:44 <jtanner> no, we're trying to make intentional coverage rather than incidental 15:17:06 <bcoca> jtanner: that is unrelated to target organization afaik 15:17:06 <jtanner> consolidation / normalization / patternization isn't a current goal 15:17:37 <jtanner> i've given my suggestion. take it or leave it 15:17:56 <bcoca> one thing i learnt during migration is that targets 'should' follow the 'tool' pattern, not use case , but i think this is tootally diff discussion and requires mattclay 15:19:28 <bcoca> cyberpear: thre are actually2 formats right now afaik 15:23:26 <bcoca> DaazKu: i would also add version added tags to docs, but otherwise, lgtm 15:24:13 <DaazKu> bcoca Sure. Just gimme the version and where it should be added and I'll do it 15:24:43 <felixfontein> version would be 2.10 15:24:50 <bcoca> `.. versionadded:: 2.10` 15:24:57 <bcoca> ^ that is the rst notation 15:25:07 <bcoca> you'll see examples of it in docs already 15:25:11 <DaazKu> Thanks. 15:26:56 <bcoca> if noone else wants to weigh in on that one. .. 15:27:03 <bcoca> #topic Open Floor 15:32:33 <bcoca> #endmeeting