optimus
optimus copied to clipboard
Refactor to use only one job spec repository instead of multiple
Description If we check the current implementation of job spec repository (referring implementation until 516c9cd72e509cd740eca7b2a342f066a67ca287), there are some repositories where we can do some operations on job spec. This could introduce confusion, such as during its usage or enhancement or whatnot.
Acceptance Criteria
- [ ] there's only one repository to operate on job spec
Out of Scope
- project spec repository being refactored
- namespace spec repository being refactored
Note: further details could be added later