I don't think adding an additional flag is the right solution, we miss a way to declare a more explicit init container and have compose manage it accordingly. service_completed_successfully unlocked a few usages but is only a partial solution

I don't think adding an additional flag is the right solution, we miss a way to declare a more explicit init container and have compose manage it accordingly. service_completed_successfully unlocked a few usages but is only a partial solution

I mean sure having a more explicit way to declare init containers, I agree, sounds like the way to go. But until that's implemented, a minor change like adding an additional flag could still be beneficial for managing init containers more effectively, right?! I think that when such a way becomes a thing, the code of this PR can be repurposed/removed easily.

such a "minor change" we would have to support and maintain for years, so I prefer to say "no" and take time to find a better way, even this takes bit more time, than making the code ever more complicated by introducing some more corner cases