-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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(backend): preserve querystring in pipeline root (fixes #10318) #10319
feat(backend): preserve querystring in pipeline root (fixes #10318) #10319
Conversation
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
Also apply to client.go
Using custom S3 endpoints now works for me. Ready for review! |
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
/cc @chensun |
* feat: remove query string from URIs
@@ -1078,12 +1079,6 @@ func provisionOutputs(pipelineRoot, taskName string, outputsSpec *pipelinespec.C | |||
return outputs | |||
} | |||
|
|||
func generateOutputURI(root, artifactName string, taskName string) string { | |||
// we cannot path.Join(root, taskName, artifactName), because root |
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.
Since now you new function is similar to the old generateOutputURI
function, it make sense to bring these comments to the changes you have at line 1065 or just update the generateOutputURI
function.
@TobiasGoerke: The following test failed, say
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. I understand the commands that are listed here. |
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.
thanks @TobiasGoerke
/lgtm
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: chensun 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 |
…10318) (kubeflow#10319) * feat: preserve querystring in pipeline root * refactor: create AppendToPipelineRoot Also apply to client.go * feat: remove query string from URIs (kubeflow#1) * feat: remove query string from URIs * refactor(GenerateOutputURI): move and preserve comments
@chensun @Tomcli @connor-mccarthy is there any chance we can cut a 2.0.6 patch release that has this PR included? It's pretty important, because external object stores can't be used with KFP v2 without query parameters (in the pipeline root URI). This will be less important if we ever get #9689 resolved, but that's a longer term fix. |
Signed-off-by: Mathew Wicks <[email protected]>
How to use custom S3 endpoints ?Can you give an example? @TobiasGoerke |
For v2 pipelines, you'll need to set the |
Signed-off-by: Mathew Wicks <[email protected]>
Signed-off-by: Mathew Wicks <[email protected]>
Signed-off-by: Mathew Wicks <[email protected]>
The kfp-driver now recognizes query params and assembles bucket names correctly.
See #10318