Isitha Subasinghe

As I stated before, we could potentially deconstruct the workflows into multiple key/value pairs @agilgur5, it is kind of an ugly solution but one that will work with no issues...

You are correct that the this will still be limited by the initial resource passed to k8s. It definitely isn't a nice solution (arguably, it is a hack) I was...

@agilgur5 Makes sense, I do like Terry's suggestion the best.

> How would key splitting work given that you cannot guarantee atomic writes to multiple objects? > > You may end up writing some status changes but then failing to...

> > we could potentially deconstruct the workflows into multiple key/value pairs @agilgur5, it is kind of an ugly solution but one that will work with no issues (well we...

Thanks for checking on this for me @AlanD88, I will re-open this in that case. I can confirm that actually using the values from step c does cause the issue...

https://github.com/isubasinghe/argo-workflows/blob/multiple-references-to-consecutive/output.txt

@terrytangyuan can you please approve: https://github.com/argoproj/argo-workflows/pull/10084 This should be fixed afterwards

@luismarques do you know if spike can print terminal output this way?

Thank you so much for your quick response @luismarques , this is super useful for me.