-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Custom artifact import #287
Conversation
@psundstrom @maraberg are you OK with the example flow above? @abhilash-kumar-nair I suggest we mark the method experimental as we probably need do bump required open api version to enable this feature. |
It looks good to me, follow the "execute" pattern with wait() operation which I like. |
@iakovn Sure! Done! |
Looks good to me to. Will there be a corresponding .get workflow to find out what custom artifacts there are for a case? Also I see a risk that you might upload artifacts to old results that you didn't intend to. This is solved if you can mark a case/experiment as finalized and then you can't change it. |
We already have an api for fetching artifacts for a case? Hmm what do you mean by Old results? A user will get an error if they try to upload a artifact with ID same as an existing ID unless they specify overwrite.(See the latest commit) |
74d47ec
to
373689d
Compare
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's get it in!
Code to test
Jira - https://modelonproducts.atlassian.net/browse/FLOW-527