-
Notifications
You must be signed in to change notification settings - Fork 55
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
Construct proper S3 URIs on register_model
#39
Conversation
ae85d22
to
e07aeff
Compare
e07aeff
to
354f12d
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.
Thank you for the iterations on this @isinyaaa !
How about a complete example of using this in clients/python/tests/test_client.py
?
to me, already
/lgtm
354f12d
to
b93c98d
Compare
Sorry, I'll update the tests now, I missed this somehow. |
Signed-off-by: Isabella Basso do Amaral <[email protected]>
Signed-off-by: Isabella Basso do Amaral <[email protected]>
Signed-off-by: Isabella Basso do Amaral <[email protected]>
b93c98d
to
515aff0
Compare
# FIXME: is this safe? | ||
return f"s3://{bucket}/{path}?endpoint={endpoint}&defaultRegion={region}" |
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.
bumping this note here now that the PR is "ready", can you share your thoughts?
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.
Looks better for uri building. Did we also want to add the URI components as individual properties to the model metadata? Maybe we can pass a metadata object to the uri builders so that it can be reused in the register call.
@tarilabs didn't UI say they would like the uri components individually, or are they happy to have the constructed uri?
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.
Thank you for having expanded on examples and tests!
per #39 (review),
/lgtm
rm = mr_client.register_model( | ||
name, | ||
uri, | ||
model_format_name="test_format", | ||
model_format_version="test_version", | ||
version=version, | ||
) |
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.
nit, but superflous; I believe here is missing storage_path, ie:
rm = mr_client.register_model( | |
name, | |
uri, | |
model_format_name="test_format", | |
model_format_version="test_version", | |
version=version, | |
) | |
rm = mr_client.register_model( | |
name, | |
uri, | |
model_format_name="test_format", | |
model_format_version="test_version", | |
storage_path="storage/path", | |
version=version, | |
) |
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.
/lgtm
@dhirajsb: changing LGTM is restricted to collaborators In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
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.
Thank you @isinyaaa
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dhirajsb, isinyaaa, tarilabs The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
* Adding wait between deployments * added 0 as arg
Description
Provides an S3 URI builder util function with overloads that it can guarantee there's no metadata (e.g. from the environment) missing upon creating MR objects, either for UI or deployment purposes.
The usage of the helper is, although, optional. Proposed usage is presented on an example on the README file.
This work is based of off: https://issues.redhat.com/browse/RHOAIENG-3979
How Has This Been Tested?
Inside the client folder, run
Merge criteria: