#3232 [Core feature] Pass inputs inline with execution event data Issue created by katrogan Motivation: Why do you think this is important? Follow-up to #1327. For a distributed propeller deployment it's useful to pass executions inputs inline rather than as an offloaded URI. Goal: What should the final outcome look like, ideally? Raw inputs should be (configurably) sent inline in execution events Describe alternatives you've considered Current implementation Propose: Link/Inline OR Additional context No response Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte