-
Notifications
You must be signed in to change notification settings - Fork 361
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
Add new Java SDK #6656
Add new Java SDK #6656
Conversation
arielshaqed
commented
Sep 27, 2023
•
edited
Loading
edited
- In this PR:
- Also publish new client
- Test both presigned and "regular" modes
- Publish this client
- In future PRs:
- Use published client in lakeFSFS build, or locally-installed build
- Add remaining tests
Also fixes #6581 by adding a minimal test that the new client SDK is cool when it sees an unknown property. This does not really test lakeFS, it tests that OpenAPI-codegen does what we wanted it to do. |
03184b5
to
0d9aef3
Compare
83d2190
to
1f34231
Compare
e13b87f
to
f125a1d
Compare
1f34231
to
6ed5dc7
Compare
bc75a9d
to
8e273bb
Compare
@arielshaqed can you please specify the files that you actually changed? |
be4d891
to
7e0efc0
Compare
96f0fbd
to
47aabdf
Compare
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.
@Jonathan-Rosenberg PTAL :-)
I now:
- Moved lakeFSFS changes to a separate PR
- Told Linguist to fold java-legacy by default (see .gitattributes change!)
- Rearranged some changes to be more logical by commit.
It should be easier to review.
@@ -0,0 +1,3 @@ | |||
# Files to ignore (skip) when generating Java client | |||
maven.yml | |||
.github/ |
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.
.github/ | |
.github/ | |
git_push.sh |
?
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.
Done, thanks!
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.
Now really re-done.
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 except for a possibly missing open-api-ignore key.
Ping me if it's intentional
78c52b4
to
2b7ab98
Compare
* New Java client to fix #6424 will go in clients/java/. * "Legacy" Java client moved to clients/java-legacy/. The new client uses a single request-object parameter. This commit does *not* include the new generated client, to allow Git to display the rename of clients/java/ to clients/java-legacy/ on this commit.
Backwards compatibility enabled by *not* verifying unknown properties.
The existing java-api-client "deploy" job should publish the new SDK. Add a job to publish the old API. We will get rid of it after releasing 1.0.
Now changes to this subdirectory will appear folded by default in PRs.
2b7ab98
to
df4cba6
Compare
I think that I added the desired openapi ignore key(?). PTAL... |
89f4cc3
to
2230176
Compare
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
Thanks! |