Handle arbitrary event payloads about triggers HOT 7 CLOSED

Could we use reflect

from triggers.

Could we use reflect

With the caveat that this is something I've heard other people say, and not something I've really experimented with myself, I'm under the impression that using reflection has a significant performance impact. (That and code that uses reflection can be a little confusing to follow!)

from triggers.

I made a quick prototype using the internal encoding/json library and map[string]interface{}

My prototype approach utilized reflect, but as mentioned, there is a considerable performance impact.

from triggers.

/assign

from triggers.

Another way to tackle this would be to initially target only creation of PipelineResources and PipelineRuns, which would reduce the scope required a bit and we could add support for arbitrary resources later (but if we can get it all at once then great!)

from triggers.

Another way to tackle this would be to initially target only creation of PipelineResources and PipelineRuns, which would reduce the scope required a bit and we could add support for arbitrary resources later (but if we can get it all at once then great!)

I understood this work item to just be the event side extraction only, which be the logic to set TriggerBinding params

from triggers.

I understood this work item to just be the event side extraction only, which be the logic to set TriggerBinding params

Oh good call! My bad, I didn't read it fully and assumed it was about specifying arbitrary templates in the Template - just ignore me 😅

from triggers.