-
Notifications
You must be signed in to change notification settings - Fork 43
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
docs(api): Add additional docs to describe behaviour of model redeployment #478
Conversation
becomes the current *deployment* of the model version. | ||
|
||
If the deployment of the new configuration fails, **the old deployment stays deployed** and remains as the current | ||
*deployment* of the model version. The new configuration will then show a 'Failed' status. |
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 thinking of adding some screenshots of the UI here to show the new deployment history panel but I don't think it's absolutely necessary here because the rest of the docs don't really show screenshots of the UI. We can still do this for a start and add UI screenshots for the rest of the docs subsequently too. What do you all think?
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 think one ss here here will do
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.
Okay, I'll see what I can find and add one here.
Okay I've just addressed the comments in this PR. Thanks a lot for the reviews! |
What this PR does / why we need it:
This PR introduces some additional user documentation to describe the new behaviour when redeploying model versions in Merlin.
Which issue(s) this PR fixes:
None
Fixes #
Does this PR introduce a user-facing change?:
Checklist