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

allow configuration of default value for remoteDatacenterFallbackEnabled #1875

Merged
merged 2 commits into from
Jul 2, 2024

Conversation

moscicky
Copy link
Collaborator

@moscicky moscicky commented Jun 21, 2024

Make a default value for topic property fallbackToRemoteDatacenterEnabled configurable via:

  • topic.defaultFallbackToRemoteDatacenterEnabled for management
  • frontend.topic.defaults.fallbackToRemoteDatacenterEnabled for frontend

This will enable configuring whether newly created topics and topics with missing property should have fallback turned on by default or not.

@moscicky moscicky marked this pull request as ready for review June 24, 2024 13:28
@moscicky moscicky force-pushed the default-remote-datacenter-fallback-enabled branch 2 times, most recently from 24e4624 to 33630c6 Compare June 25, 2024 06:27
@moscicky moscicky force-pushed the default-remote-datacenter-fallback-enabled branch from 33630c6 to b9dfb09 Compare June 25, 2024 11:37
//then
response.expectStatus().isOk();
Topic t = hermes.api().getTopicResponse(topic.getQualifiedName()).returnResult(Topic.class).getResponseBody().blockFirst();
System.out.println("Aaa");
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this was for debugging purposes 😛

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

removed

@moscicky moscicky merged commit 1e634b4 into master Jul 2, 2024
27 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants