Skip to content
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

feat(RegisterModel): 9914 autofill connection #3084

Conversation

gitdallas
Copy link
Contributor

closes: https://issues.redhat.com/browse/RHOAIENG-9914

image
image
image
image
image
image
image

Description

On the register modal page, there will be a new button to the right of Model Location / Object Storage (when selected) that says "Autofill from data connection".

Clicking that should bring up a modal with a project selector and a data connection selector. Selecting a project will populate the data connection selector with it's available data connections that contain a bucket.

Selecting a data connection and hitting the submit button will populate the Object Storage region/endpoint/bucket in the register model form.

How Has This Been Tested?

Made sure that projects appear in project selector, and data connection is disabled with a note about selecting a project.
Upon selecting a project, data connection will either be populated or remain disabled with a note that the project does not contain any data connections.

Selected multiple data connections and made sure that the form populated with data from that data connection.

Test Impact

Added tests to the register model to check that the button appears when it should, the modal appears when the button is clicked, the correct labeling/content appears in the dropdowns, and the fields get populated correctly.

Request review criteria:

Self checklist (all need to be checked):

  • The developer has manually tested the changes and verified that the changes work
  • Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
  • The developer has added tests or explained why testing cannot be added (unit or cypress tests for related changes)

If you have UI changes:

  • Included any necessary screenshots or gifs if it was a UI change.
  • Included tags to the UX team if it was a UI/UX change.

After the PR is posted & before it merges:

  • The developer has tested their solution on a cluster by using the image produced by the PR to main

Copy link
Contributor

@mturley mturley left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A couple small things

Signed-off-by: gitdallas <[email protected]>

squash me

Signed-off-by: gitdallas <[email protected]>

squashme

Signed-off-by: gitdallas <[email protected]>
Signed-off-by: gitdallas <[email protected]>
@gitdallas gitdallas force-pushed the feat/9914-connection-autofill branch from c2bd685 to d0f27ec Compare August 15, 2024 20:52
Copy link
Contributor

@mturley mturley left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great stuff. Thanks @gitdallas

Copy link
Contributor

openshift-ci bot commented Aug 15, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mturley

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-bot openshift-merge-bot bot merged commit e454189 into opendatahub-io:main Aug 15, 2024
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants