-
Notifications
You must be signed in to change notification settings - Fork 53
[WIP] Use custom model name in deployment #1236
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
base: main
Are you sure you want to change the base?
Conversation
ads/aqua/model/model.py
Outdated
@@ -147,6 +147,7 @@ class AquaModelApp(AquaApp): | |||
def create( | |||
self, | |||
model_id: Union[str, AquaMultiModelRef], | |||
display_name: Optional[str] = None, |
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.
It can be risky to insert attributes in the middle of an existing list, as it may lead to unintended side effects or compatibility issues. A better practice is to append new attributes at the end of the list .
…le/accelerated-data-science into use_custom_model_name_in_deployment
@@ -204,6 +207,9 @@ def create( | |||
**(defined_tags or {}), | |||
} | |||
|
|||
if display_name: |
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.
I’m not sure I understand the logic here. I thought we wanted to introduce the model name that would be used for inferencing, but here we’re changing the display name of the MC record.
Could you add more description in the PR explaining what this PR for?
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.
+1
Description