Eyal Mor

Fix for #810 due to deep copy introduction in Pydantic. It seems like pydantic 1.9.1 added deepcopy to model validation: ``` Config.copy_on_model_validation does a deep copy and not a shallow...

Currently results are processed in the backend TestRemote implementation. That means that there is only one data representation that is generated. We would like to have a data structure to...

The current implementation of the E2E testing renders the test results in a string and prints that to the screen. This isn't really usable in CI scenarios where structured data...

The current CLI implementation lacks the DevX polishing to allow developers to easily read the outputs in-case of a success/error. Find a way to color the output easily in the...

The current implementation of the `SavePipeline` command assumes implements the happy path only. This may lead to inconsistent states where in `Nested Pipelines` the child pipelines are updated without the...

Give a name change, pipelines will remain orphaned in an application. This could cause confusion or worse, a trigger of the wrong pipeline may produce inconsistent application states in prod....

Current implementation of the nested pipeline save uses a naive DFS implementation. Meaning, each new pipeline stage & pipeline is saved sequentially. For highly nested pipelines or pipelines with many...

Currently missing parameters are not easily testable. During manifestation of JSonnet, params are read from Render.yaml and passed to the render. Missing parameters aren't debuggable due to the amount of...

I took the exec/E2E yaml files from the generic example and tried to adapt to a given project. it would be nice if the error message or some docs existed...

Original Author: @dkirillov We should figure out how the E2E testing behaves and the interface for it - specifically around `expected_output` and the various stage output cases. Some things that...