Choosing coroutineScope vs supervisorScope for a multi-step deployment pipeline without silent sibling cancellation
I'm structuring a Kotlin deployment pipeline as a set of concurrent rollout steps (config push, service restart, health check) using kotlinx.coroutines. The documented behavior is clear in isolation: a failing child in a regular coroutineScope cancels all siblings and propagates the exception, while supervisorScope lets siblings finish and requires each chil
kotlin