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

Enables uploading a pipeline via a URL #554

Merged
merged 1 commit into from Dec 18, 2018

Conversation

rileyjbauer
Copy link
Contributor

@rileyjbauer rileyjbauer commented Dec 17, 2018

This change is Reviewable

@rileyjbauer
Copy link
Contributor Author

/assign yebrahim
/area front-end

Still needs verification on real cluster
Copy link
Contributor

@yebrahim yebrahim left a comment

Choose a reason for hiding this comment

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

LGTM, just one minor comment.

</div>
<Input onChange={this.handleChange('fileUrl')} value={fileUrl} required={true} label='URL' />
</React.Fragment>
)}

<Input id='uploadFileName' label='Pipeline name'
Copy link
Contributor

Choose a reason for hiding this comment

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

We should remove the upload parts of the id and the state field here since they're also used in url import path.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Hm, I don't disagree, but the entire component is based around that name (UploadPipelineDialog). I'm up for renaming it in a follow-up, but what's a better verb? Add?

Copy link
Contributor

Choose a reason for hiding this comment

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

Good point, probably good to handle that separately if we see the need.

/lgtm

@yebrahim
Copy link
Contributor

/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: yebrahim

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

1 similar comment
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: yebrahim

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

@yebrahim
Copy link
Contributor

/test kubeflow-pipeline-e2e-test

@k8s-ci-robot k8s-ci-robot merged commit 58bb9af into kubeflow:master Dec 18, 2018
@rileyjbauer rileyjbauer deleted the upload-pipeline-via-url branch May 6, 2019 22:16
magdalenakuhn17 pushed a commit to magdalenakuhn17/pipelines that referenced this pull request Oct 22, 2023
* Updated roadmap for 0.3 and 0.4

* more changes

* blah

* merged

* typo
HumairAK pushed a commit to red-hat-data-services/data-science-pipelines that referenced this pull request Mar 11, 2024
* Merge KFP changes between 1.5.0-rc.2 and 1.5.0

Resolves kubeflow#554

* Resolve backend and manifest conflicts

* Resolve frontend conflicts
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.

None yet

3 participants