Is your feature request related to a problem? Please describe.
In the current architecture, schemas needed for a job (like schemas defining the input config for a job) are currently defined within the job folder. However, they should be used within lumigator to format the job config command line params instead of using templates.
Describe the solution you'd like
A separate package (as sdk and schemas are available right now) holding job-specific schemas. When a new job would be added, the lumigator-specific packages would not need to be updated, only the job-specific config package.
Describe alternatives you've considered
Dynamic import (importlib) of job-related schemas directly into the backend and sdk.
Is your feature request related to a problem? Please describe. In the current architecture, schemas needed for a job (like schemas defining the input config for a job) are currently defined within the job folder. However, they should be used within lumigator to format the job config command line params instead of using templates.
Describe the solution you'd like A separate package (as
sdkandschemasare available right now) holding job-specific schemas. When a new job would be added, the lumigator-specific packages would not need to be updated, only the job-specific config package.Describe alternatives you've considered Dynamic import (
importlib) of job-related schemas directly into the backend and sdk.Additional context N/A