Add ability to upload artifacts to experiments via the UI

[bash-42]

Currently, artifacts can only be uploaded by the SDK. It would be helpful for a user to be able to upload artifacts directly in the UI for the experiment they are modifying.

[ainoam]

Thanks for suggesting @bhood2!

Can you elaborate on the use case: Which artifacts are you modifying, and to what end? How does your code handle such changes?
Such a solution would ideally support different storage services (ClearML file server/AWS S3/GCS etc.) - How did you consider circumventing CORS restrictions in uploading files across domains?

[bash-42]

Our use case was to be able to add additional artifacts (think training models) to an existing experiment and store them in AWS S3 for future use. I'm not actually modifying the artifact, simply adding new ones to an experiment. The code takes the raw file and uploads it to S3 then updates the experiment in the DB with the new artifact information. The code could easily support additional storage services with minimal modifications.
For the CORS restrictions, S3 has editable CORS settings where I added our ClearML domain. However, this is bucket specific and I cannot upload to a bucket that doesn't recognize the ClearML domain.

[ainoam]

Thanks for the added insight @bhood2.
Wondering what's compelling you to explicitly add these models post training? (ClearML should be capturing all models trained...)
If these were not generated by that task, wouldn't an "import" capability in the model table be a better fit?

[bash-42]

Thank you for the reply @ainoam.
I have asked my coworkers to elaborate on the use cases where this feature is desirable and they have informed me that this feature is not for uploading the models, but for uploading supporting files for the models. For each model artifact, the user may want to have numerous supporting files. For example, a user has a model trained in an experiment and they want to add a model wrapper file such as a python file that wraps the model into another class supported by another experiment (training or deployment). Another example is with a model serving with the original clearml-serving stack, the user would use the CLI to upload the preprocess file for the model (similar to the wrapper, providing standard interfaces) and this feature is the only way to add this file as an artifact. One further example, in training if the user wants to change a complete training configuration (not a single value) with a YAML configuration file, the user can only make the change through the source code and then they have to track unnecessary configuration changes. This feature will allow the user the ability to do everything needed to an experiment within the UI.