Re: Introducing Flight Deck: Infrastructure-as-Code for Debian Go Team Repositories

[Nilesh Patra <nilesh@debian.org>]

Hi,

I don't know how much value my feedback holds here. As such, I am
not a devops engineer (at least professionally) and I had to do a bit
of reading to understand what this tool is doing.

First off, I have 3 quick questions:

- Do I have to add in a hcl file for each package individually for
  flight-deck to configure it?

- Is there a way to enable it across all packages where I am listed
  as an uploader in?

- Does it have any significant advantages over existing workflow?

Unless I misunderstood, the eventual functionality is somewhat similar
to what one would achieve with dh-make-golang and existing tools in
devscripts, no?

I don't have strong opinions about using or not using flight-deck (in fact
no strong opinions about anything-software in general) and I am all in for giving
it a try. But I am a little reluctant to spend time on it unless there are significant
benefits -- and I'd be happy to hear you.

Also, just a suggestion: it would help if you describe the features first and
how it works later in the readme. I ended up reading a bit of documentation
about opentofu which probably wasn't needed, but it never hurts to read more :P

And a couple of example commits (in the readme) on how to enable
it (on example packages) could be helpful.

Thanks for your work,
Nilesh