Skip to content
Reintroduce the gitlabci_runner_config data source

Being able to programmatically construct runner configurations is rather
nifty. (At least, I think so.) The prior way this was implemented was,
shall we say, not sustainable.

Poking around the traefik source one day, I realized I could leverage an
internal tool of theirs to take the, um, modularly awkward
gitlab.com/gitlab-org/gitlab-runner/common and its useful configuration
structs and spew those structs out somewhere we could take advantage of
them. Past that, we can generate other code using the generated code
(insert evil laugh here) to handle the terraform schemas and read
methods necessary.

There's still some improvement to be done (the second-level code
generator is ... um, messy), but I believe it's at a point we can start
taking advantage of it. (Again.)