We're using the app to provision AL2023 runners, and would like to start offering multiple runners with differing AWS machine types. The multi-runner option seemed like the obvious solution, but if we specify a list of machine types in a runner template, they will share the same extra label.
One option would seem to be the use of two different template files, both for AL2023, and each with a distinct machine type and associated label.
Another option might be to include multiple packer files in the build, each specifying the corresponding machine type and label. Would both AMIs be served by the webhook in this scenario?

I'll be experimenting on these approaches, but wanted to see if I am duplicating work and/or wasting my time. :-) Any feedback appreciated!