Wednesday, 2019-04-24

*** gvincent has joined #ara08:45
*** gvincent has quit IRC08:46
*** gvincent has joined #ara08:47
*** gvincent has quit IRC09:11
*** sshnaidm|afk is now known as sshnaidm|09:16
*** sshnaidm| is now known as sshnaidm09:16
*** gvincent has joined #ara09:24
*** odyssey4me has joined #ara09:42
larsksdmsimard: would it be useful if ansible objects (playbooks, tasks, etc) had a "description" field that could be used like a python docstring? I figure ara could use that in the ui to provide additional information about plays, tasks, etc.12:44
ara-slackchief_wrench: Isn’t that what the name: property is for?12:45
dmsimardlarsks: there's a thing called "labels" that I'd like to be a thing in 1.0 that isn't exactly what you're asking for but I was asking myself it it would be relevant to apply to other objects than just playbooks12:46
dmsimardlabels are generic and would be used to create arbitrary groups of playbooks (or hosts, or tasks, or...)12:46
larsksdmsimard: I'm asking because I've always wanted documentation like that to be a first-class object in playbooks rather than comments so that it can be machine-accessible, and it turns out the change is basically a single line of code to ansible.12:47
larsksCurious if other folks would find it useful or if it's just me.12:47
dmsimardlarsks: how would you see that working in practice ?12:47
dmsimardwould it be an ansible variable ?12:47
larsksNo, just a new attribute on plays, tasks, etc.  In addition to 'name', you could have e.g. 'description'.  Like this: https://gist.github.com/larsks/e6e2ff29873716fc2aaa04a129904ebd12:48
larsksI figured a tool like Ara would be able to use that information to (optionally?) display play/task/etc documentation in the UI.12:49
dmsimardI agree with @chief_wrench that it overlaps a bit with name but we can argue that the name would be succint while the description would be verbose12:49
dmsimardif description gets added to ansible, ara can definitely pick it up and display it12:49
larsksRight, but the question I am asking is more along the lines of "do you think this is a useful idea or am I barmy?"12:50
dmsimardah, apologies, was looking at it from an ara perspective12:51
larsksWell, that's part of the question, right? Do you think having access to extended documentation like this be useful to Ara.12:52
dmsimardI make a distinction between what would be useful to ara and what would be useful to users :p12:54
dmsimardI mean, the point of the description field would be to allow users to better understand what the play or task was about12:54
*** irclogbot_3 has quit IRC12:55
*** irclogbot_2 has joined #ara12:55
larsksRight, but arguably you can get that from comments as well.  I see the primary benefit being making this information available in a machine-readable fashion.12:56
*** altlogbot_2 has quit IRC12:57
dmsimardwhat you linked is just a string, though12:57
dmsimardwould you see description becoming something more than a string ?12:57
*** altlogbot_2 has joined #ara12:57
dmsimardfor example, zuul has some documentation concepts to describe different ansible roles and jobs12:58
larsksI was not assuming it would be any more structured than a string, no, other than that the string could be markdown.12:58
dmsimardok, just to give you an idea of what I meant with Zuul: https://opendev.org/zuul/zuul-jobs/raw/branch/master/roles/build-docker-image/common.rst which gets rendered as https://zuul-ci.org/docs/zuul-jobs/container-roles.html#role-build-docker-image13:01
larsksSure, but that's just like dropping a README.md next to your python code: you probably still use docstrings in your classes and functions.13:04
larsksAnyway, it sounds like your opinion is mostly "meh", which is fine. I was really just looking for an opinion other than my own :)13:05
dmsimardlarsks: Over time I have disciplined myself to try and give good names to plays and tasks (even if they end up being a bit verbose)13:06
dmsimardI see the use case for the description field. I would use it when I need it (where I would have otherwise put a comment, perhaps) but not for every task.13:06
dmsimardIf it ends up landing, there's no problem to make it available in ara13:09
*** dbpiv has joined #ara13:38
*** bwatson has quit IRC13:55
*** etienne has quit IRC14:29
*** spiette has quit IRC14:52
*** spiette has joined #ara14:54
*** etienne has joined #ara15:12
*** sshnaidm is now known as sshnaidm|off15:23
*** dbpiv has quit IRC15:35
*** altlogbot_2 has quit IRC16:09
*** altlogbot_3 has joined #ara16:11
*** altlogbot_3 has quit IRC16:43
*** altlogbot_1 has joined #ara16:43
*** altlogbot_1 has quit IRC16:53
*** altlogbot_1 has joined #ara16:53
*** gvincent has quit IRC17:11
*** gvincent has joined #ara18:31
*** gvincent has quit IRC18:36
*** gvincent has joined #ara18:36
dmsimardapollo13: have you seen this kind of error before ? tox is suddenly confused about pyproject.toml and setup.py: https://github.com/ansible-community/ara/issues/3321:45
*** etienne has quit IRC21:52

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!