News for hackers. Stuff that matters.
Re:Write Gitlab CI Pipelines in Python Code by AlphaSite on Friday April 30, 2021 @02:29AM (#26990390)
YTT is pretty nice too and basically glues star lark and yaml together.
Re:Write Gitlab CI Pipelines in Python Code by sofixa on Friday April 30, 2021 @03:26AM (#26990695)
via comments! YAML is an abomination in itself ( spaces for logic?!), the last thing it needed was comments for extra logic.
Re:Write Gitlab CI Pipelines in Python Code by AlphaSite on Saturday May 08, 2021 @06:03PM (#27091175)
Not actually via comments, they just use the same syntax, im pretty sure the pretemplated code is not actually valid yaml.
Re:Write Gitlab CI Pipelines in Python Code by xdennis on Friday April 30, 2021 @04:58AM (#26991204)
Proper spacing makes code readable. Forcing it is a good thing.
Re:Write Gitlab CI Pipelines in Python Code by guipsp on Friday April 30, 2021 @05:05AM (#26991255)
It's a good thing, until you ask a non-technical user to edit the config file. Then they become confused because a tab is visually, but not functionally equivalent to a number of spaces.
Re:Write Gitlab CI Pipelines in Python Code by erinnh on Friday April 30, 2021 @05:19AM (#26991322)
I wouldnt ask a non-technical person to write any of these config files.

If I want non-technical people to configure something I need to write a GUI for self-serving.

Re:Write Gitlab CI Pipelines in Python Code by sofixa on Friday April 30, 2021 @09:11AM (#26992940)
Indeed, it does, when done via something like go fmt. But in the case of YAML, a pedantic level of "proper spacing" is used for logic. 2 or 3 spaces shouldn't change the meaning and order of things