-
Notifications
You must be signed in to change notification settings - Fork 116
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
[Catalog] Use production config+tree resources from Nessie Catalog #8539
[Catalog] Use production config+tree resources from Nessie Catalog #8539
Conversation
The Nessie client used from Nessie Catalog is currently a "simple" one. This change lets it use a client that's configured against the actual config+tree resources, which also perform authZ.
@@ -32,6 +32,7 @@ dependencies { | |||
implementation(project(":nessie-versioned-storage-common")) | |||
implementation(project(":nessie-versioned-storage-inmemory")) | |||
implementation(project(":nessie-versioned-storage-store")) | |||
implementation(libs.guava) |
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.
Shall we move the combined client out of the testing
folder?
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.
Want to do that, but in a separate PR.
return new CombinedClientBuilder() | ||
.withConfigResource(configResource) | ||
.withTreeResource(treeResource) | ||
.buildForProduction(NessieApiV2.class); |
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.
Do we really need the new method? Calling the old build
method would yield the same result.
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.
Wanna give that another look separately. Potentially removing the code path in build()
if it's not used anywhere.
d5dee3e
into
projectnessie:feature/nessie-catalog-server
…8539) The Nessie client used from Nessie Catalog is currently a "simple" one. This change lets it use a client that's configured against the actual config+tree resources, which also perform authZ.
…8539) The Nessie client used from Nessie Catalog is currently a "simple" one. This change lets it use a client that's configured against the actual config+tree resources, which also perform authZ.
…8539) The Nessie client used from Nessie Catalog is currently a "simple" one. This change lets it use a client that's configured against the actual config+tree resources, which also perform authZ.
…8539) The Nessie client used from Nessie Catalog is currently a "simple" one. This change lets it use a client that's configured against the actual config+tree resources, which also perform authZ.
…8539) The Nessie client used from Nessie Catalog is currently a "simple" one. This change lets it use a client that's configured against the actual config+tree resources, which also perform authZ.
The Nessie client used from Nessie Catalog is currently a "simple" one. This change lets it use a client that's configured against the actual config+tree resources, which also perform authZ.