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

lakectl endpoint configuration without path level version #6542

Closed
nopcoder opened this issue Sep 4, 2023 · 0 comments · Fixed by #6609
Closed

lakectl endpoint configuration without path level version #6542

nopcoder opened this issue Sep 4, 2023 · 0 comments · Fixed by #6609
Assignees
@nopcoder
Labels
v1.0.0-blocker Issues that should be closed before going out with v1.0.0

Comments

@nopcoder
Copy link
Contributor

nopcoder commented Sep 4, 2023 •
edited
Loading

As part of v1 the configuration of lakectl endpoint should not include "/api/v1"
The lakectl should warn the user to drop the path and auto-configure the base endpoint version base on the client API version.
This change also require going over our current documentation, samples and code we provide as example.
@nopcoder nopcoder added the v1.0.0-blocker Issues that should be closed before going out with v1.0.0 label Sep 4, 2023
@nopcoder nopcoder changed the title lakectl endpoint configuration should compatability lakectl endpoint configuration without path level version Sep 11, 2023
@nopcoder nopcoder self-assigned this Sep 13, 2023
@nopcoder nopcoder mentioned this issue Sep 15, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@nopcoder nopcoder

Labels
v1.0.0-blocker Issues that should be closed before going out with v1.0.0
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

lakectl endpoint configure and endpoint path reuse treeverse/lakeFS
1 participant
@nopcoder