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.

Sign up for GitHub

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

Jump to bottom

[feature] Expose existing_token in KFP CLI #11399

Closed
tumido opened this issue Nov 22, 2024 · 1 comment · Fixed by #11400
Closed

[feature] Expose existing_token in KFP CLI #11399

tumido opened this issue Nov 22, 2024 · 1 comment · Fixed by #11400
Labels
area/sdk kind/feature

Comments

@tumido
Copy link
Contributor

tumido commented Nov 22, 2024

Feature Area

/area sdk

What feature would you like to see?

In Python SDK there's an kfp.Client's property called existing_token. This argument comes very handy in environments where KFP uses external auth providers etc. KFP CLI is unusable in these environments, since its users can't use --existing-token option there.

What is the use case or pain point?

Being unable to use KFP CLI simply because there's one missing option which exists in the underlying SDK is very unfortunate.

Is there a workaround currently?

Users have to use Python SDK's kfp.Client directly.

Love this idea? Give it a 👍.
@tumido tumido mentioned this issue Nov 22, 2024
Merged
2 tasks
@tumido
Copy link
Contributor Author

tumido commented Nov 22, 2024

Tbh, I'm not sure if this is even a feature request or a bug report. 🙂

Anyways, I think this is very simple to implement anyways.. here's a PR: #11400

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/sdk kind/feature
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat(cli): expose existing_token client property tumido/kubeflow-pipelines
1 participant
@tumido