There's a lot of disparity between our YAML variables names (input arguments) and CLI arguments. It makes YAML task writing a very confusing task.
Current state: | CLI input argument | YAML variable name | |----|----| |koji_build|envr| |bodhi_id|bodhi_id| |koji_tag|tag|
Of course, the fact that this mapping is not documented anywhere doesn't help this a bit. But even if it was documented, I see no good reason to have these large differences between the two. I think that YAML variables names should exactly match CLI input arguments.
Either make the naming consistent, or think of a different way how to make the YAML variables names obvious.
Setting high priority, because this impacts user API.
This ticket had assigned some Differential requests: D110
Please note that CLI input arguments match what taskotron-trigger and buildbot use (koji_build, bodhi_id, koji_tag).
True, but libtaskotron isn't consistent with arg names internally. For the example of koji tags, sometimes it's koji_tag and other times it's 'tag'.
Login to comment on this ticket.