YonDu

@K1ngram4 @barnettZQG User defined cues may be complex, and the trigger modification image is not very friendly. https://github.com/oam-dev/kubevela/blob/c298c98f251a613ede911c3bdbf84c0640b54c51/pkg/apiserver/rest/usecase/webhook.go#L231-L235 I suggest adding the jsonpatch field when defining trigger instances. ex: https://github.com/oam-dev/kubevela/blob/c298c98f251a613ede911c3bdbf84c0640b54c51/pkg/apiserver/rest/apis/v1/types.go#L354-L365...

Orgnization/Company: 育儿网 Location: Nanjing, China Contact: [email protected] Purpose/Scenario: Simplify application publishing, CD, CI with kubevela Features wanted: 1、Robust workflow and more flexible custom workflows 2、Kubernetes resource status collector

support，In fact, there has been a similar demand recently

> 我查看了 exec.Cmd 必须提供的内容，似乎他们有一个`StdinPipe`可以用来解决问题的东西。我已经更新了我的[演示存储库](https://github.com/joepadmiraal/cmd-test)，并提供了一个说明其工作原理的示例。 > > 更改 go-cmd 实现以开始使用是否有意义`StdinPipe`？ 或者也许我们可以简单地暴露`StdinPipe`, `StdoutPipe`and `StderrPipe`？ I also encountered the same problem ， are you have resolved the issue? Looking forward to your sharing.

I also have the same question .

+1