#33 Integration testing suite v1 Pull request opened by zeryx This PR adds the

integration.py

script and

runIntegration.yaml

CI workflow. When a PR is made against main, the runIntegration workflow will trigger. This workflow will automatically generate new images if the code has changed in any particular template. It it will then execute integration.py to automatically deploy and execute (with default inputs) all template workflows on a particular cluster. If the registration and executions succeed, then the workflow returns true - a new tool for end-to-end integration of flyte changes. built originally on the following branch: zeryx#1 And the action successfully triggered; as can be seen here: https://github.com/zeryx/flytekit-python-template/actions/runs/4886507399 With the following outlining the ghcr.io image repository that was leveraged for this personal fork testing. https://github.com/users/zeryx/packages/container/package/flytekit-python-template Considerations • Dynamic Workflows cannot be executed with default parameters, which as of v1 this only accepts default parameters; means Dynamic Workflows are not supported. • Dynamic Tasks have a bug associated with them: flyteorg/flyte#3639, which does not allow for Remote Executions of normal workflows that contain dynamic tasks to be executed. Until this issue is resolved, Dynamic Tasks are not supported. flyteorg/flytekit-python-template ✅ All checks have passed 4/4 successful checks