Executor: figure out the best way to configure which registration container to use
Currently, the machine registration container is a one-size-fits-all one... but not every farm will want to have the same machine tags or runner names. So, let's figure out the cleanest way to allow farm owners to specify which container to use for registration / check / ...
Here are a couple of possibilities:
- Use an environment variable to configure the container name:
- Pros: Less configuration needed, and job descriptions can remain what they are
- Cons: Less flexibility in the boot configuration
- Use an environment variable to override the location of the job templates
- Pros: Allows users to fully takeover the boot configuration for Sergent Hartman
- Cons: Requires more up-front work?
- Copy the default files on first boot in /config, and let the farm owner maintain them
- Pros: Brings ease of deployment and sane defaults, which can easily be overwritten by users
- Cons: Puts more strain on the machine registration container's interface being immutable
Cc: @jasuarez