Is the 'runners' module still used when using the multirunners module?

[bob-ashforth-sp]

The instructions on use of the multirunners module are quite sparse. I'm digging through code, but so far am not sure if I should remove the runners module, or revert it to all default code. Any info appreciated.

[bob-ashforth-sp]

@npalm, it looks like you are either the creator of or strong contributor to the multi-runner module. I'm trying to use it (creatively, to get multiple linux64 runners with distinct extra_labels for different machine types), and am trying to infer the correct arguments to pass the module. Since the examples don't provide an example of the top-level main.tf calling the module, there is no pattern to follow.
I'm using config files under the templates folder, and don't know what to pass as 'multi_runner_config'.
I need to get at least one additional machine type (with a distinct label) to add to our GitHub Actions options, and if the multi-runner approach takes too much longer I'll have to resort to adding another GitHub App for this purpose... not the ideal, but it would get the job done.
I hope you can provide this info without much delay... and perhaps consider adding a sample snippet of how to call the module from main.tf to the README.md and/or the examples code.

[bob-ashforth-sp]

I've found the Terraform way to decode a yaml file into a Terraform object... but since the multi_runner_config arg to the multi-runner module seems to be a single object, rather than an array/set of objects, I'm at a loss regarding the use of multiple config files/objects to generate multiple types of runner.

[bob-ashforth-sp]

So as I coninue to pore through all of the multi-runner files, I discovered that the content of main.tf in the actual multi-runner module is starkly different from what is in the examples code. I'm making progress mining the example code for what I need, but am not very experienced with Terraform and am struggling with getting declarations correct.