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.

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

Merged

Conversation

snazy
Copy link
Member

@snazy snazy commented May 20, 2024

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.

@snazy snazy marked this pull request as draft May 20, 2024 08:44
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.
@snazy snazy marked this pull request as ready for review May 20, 2024 09:19
@@ -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)
Copy link
Contributor

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?

Copy link
Member Author

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);
Copy link
Contributor

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.

Copy link
Member Author

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.

@snazy snazy merged commit d5dee3e into projectnessie:feature/nessie-catalog-server May 21, 2024
16 checks passed
@snazy snazy deleted the use-real-resources branch May 21, 2024 10:30
snazy added a commit that referenced this pull request May 24, 2024
…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.
snazy added a commit that referenced this pull request May 25, 2024
…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.
snazy added a commit that referenced this pull request May 25, 2024
…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.
snazy added a commit that referenced this pull request May 27, 2024
…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.
snazy added a commit that referenced this pull request May 27, 2024
…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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants