Store Backend Config in Run
Summary
As mantik user, I want to be able to specify my environment and parameters so I can run in different environments, with different amounts of resources and with different parameters.
Acceptance Criteria
-
The unicore-backend of each run is stored in the database. -
The entry-point of each run is stored in the database. -
The parameters of each run are stored in the database
Given a run is stored in the database,
When the run is triggered,
Then the unicore-backend, entry point and parameters can be loaded from the database.
Given a user inserts a run,
When it specifies run fields,
Then the unicore-backend, entry point and parameters can be specified.
Technical Information
Additional Notes / Information
Suggested Implementation
-
Implement the backend config to be a json blob in the run database schema. -
Implement the parameters to be a json blob in the run database schema. -
Implement the entry point to be a string in the run database schema. -
Modify the run spec to account for these changes. -
Modify the run pydantic model to account for these changes. -
Modify src/mantik_api/invoke_compute_backend/backend_config.py to account for these changes.
Edited by Sara Ansari