We have a scenario where we want separate dev/stage/beta/prod pipelines that can all be ran independently. Currently, we allow a successful dev pipeline to trigger the stage pipeline. However, in the future, we'd like a successful stage pipeline to then trigger the beta pipeline and beta to trigger prod. We cannot currently do this as Harness gives a yaml compliation/validation error at the dev level that it does not support 'nested pipeline triggers'.

Is this something that Harness could support? Or do you have suggestions on alternative ways to keep independent env pipelines but also be able to have one 'uber' pipeline that could successfully run all 4 in sequence?