marcosvm / commander Goto Github PK

Create Dockerfile to produce a container image with a statically linked executable for linux/amd 64. We want a multistage build and to keep the image as small as possible.

MVP use case, read a YAML or JSON file with a list of commands and arguments and execute them sequentially.

Add an option to run commands in parallel, the command input could have a flag parallel = true or the likes indication that this command can be run in parallel.

Note that this feature will make a significant change on the current design, introducing async execution, a runtime, etc but it'll also allow for a easier introduction of timeouts and retries later on.

Add timeouts and retries for a a command, as well for the whole execution:

• each command can have a timeout specified in seconds and/or milliseconds
• each command can have a number of retries in case it fails
• the whole execution should have a total timeout set ? Or leave it for the orchestration layer?

It would be interesting to have for each command executed:

start time, end time, elapsed time, command line, arguments, exit status

This information could be displayed via log/env_log so it can be redirected properly when executed in containers or Kubernetes pods or both.