optimus
optimus copied to clipboard
feat : `JobRunInput` api Integrate with `Init Containers`
Description Integrate the JobRunInput api with Init Containers
Acceptance Criteria
- [ ] Init containers working with
JobRunInput
- [ ]
RegisterInstance
api triggered without asset fetch request, for backward compatibility - [ ]
RegisterInstance
kept as a fallback for failedJobRunInput
requests,JobRunInput
will fail for old job run replays(i.e. those for which notify event has never been triggered)
Depends on : https://github.com/odpf/optimus/issues/405
Tech Details
- Use both "RegisterInstance" and "JobRunInput" for now
- "RegisterInstance" being the fall back for "JobRunInput" in cases where the jobRunInput fails
- also "RegisterInstance" API should be triggered irrespective as well (with a flag telling not to provide compiled assets), for data persistence in job_run_old table , this is required for rollback.