> discussions have been trending back to just using configuration structs, rather than any of the other fancy options proposed over the years. It may look a li

> discussions have been trending back to just using configuration structs, rather than any of the other fancy options proposed over the years. It may look a little more fat, and probably copies some fields that will end up in configuration but... 1. Go is very adept at copying large structures 2. A fully scaffolded struct is far easier to read than something hidden inside a function somewhere