9 Commits

Author SHA1 Message Date
74bbc9dad8
Implement rudimentary dependency model with start_order
Any container definitions in ccl.toml can be given a `start_order` tag
(integer). It is recommended to not put a start_order unless a container
depends on another one (e.g. synapse needs postgres), in which case all
dependents and dependees should be given a `start_order`, with dependees
having a lower number than their dependents. It is guaranteed that the
dependees will be started first, although the container startup
procedure is outside of our control. Containers without a `start_order`
will have their operations applied asynchronously, but those with
a start order are started, well, in order from lowest to highest. "Stop"
operations are applied in the reverse order.
2022-08-12 21:16:55 -05:00
e56d2c12d2
Rename getAndExecute -> execForEach 2022-07-31 00:57:18 -05:00
0fbb9fdec1
Improve logging and output formatting with CommandSet 2022-07-30 14:26:23 -05:00
4f78efe42c Multithread all libpod actions 2022-07-29 23:07:19 -05:00
04e108100a
Refactor command execution 2022-07-29 19:42:46 -05:00
ddd391c8b0
Mask disabled category from action by default 2022-07-27 21:48:47 -05:00
c5dc8ba3ed Clean up error handling, logging, and completion 2022-07-26 15:22:38 -05:00
d36f1ac0d5 Fix lint issues 2022-07-19 11:26:14 -05:00
f74dc50392
Rest of commands; tooling including conditional command types 2022-07-18 19:47:05 -05:00