🐛 report: hurrdurr mistakenly tries to set already set project variables
We've noticed that latest hurrdurr runs fail on us, specifically it seems to be trying to set project variables on projects where said variables.... are already set.
Digging a little bit deeper (running it with -trace
enabled), showed us that hurrdurr seems to not have filled the project struct with the variables, thus it (correctly) assumes they have to be set (because they are in the config).
Trying to figure why it does that (and doing a bit of regression testing to figure out what commit introduced this behavior), we pinpointed this one. Trying to understand why simple output might have made a difference here, we think that it's likely that this piece of code is misbehaving, likely due to the absence of the project fields Archived
and JobsEnabled
(whose absence mistakenly evaluates to false
values?) and we end up never fetching any secret variables for any projects
I suppose the fix is to resignedly return to nonsimple output (man this would've been a simple fix if only go-gitlab
used graphql, am I right? just pick the fields you want and off you go...