Hi,
I don't think another layer of terraform complexicity is any helpful
for us. Keeping things simple is better. I am generally all for modern
tooling and all that, but this dev-ops-ification basically feels like
a completely unnecessary addition of complexicity and abstraction
layer on top of everything else we already have. On top of the supposed
benefits here, with how terraform state management and whatnot works,
it is just as easy to completely destroy resources with a single
mistake as well. It is not like office work where few infra people manage
I make sure to have those guardrails in place to make the flight-deck not be able to be
destructive so you never might be able to delete repos for example only stop tracking/updating it.
everything and others wait for their check and approval to get
anything done at all (and even then people mess up a lot).
The approval from others is not required for doing actions,
the idea of open merge request is for the pipeline to run and
show you the plan of changes before you merge.
That is all my personal feelings though, others might have differing
opinions. It is a idea, but I don't really find it fitting for debian
usage. I am not buying into this particular single source of truth idea.
--
Best,
Ananthu