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

Config: add a new no-op discovery type #46

Merged

Conversation

huikang
Copy link
Contributor

@huikang huikang commented Jan 8, 2025

As we are using an in-house service discovery mechanism, we need to set the GUBER_DISCOVERY_TYPE to something other than the existing list.

This PR adds a new discovery type named embedded such thatit allows us to embed gubernator and manually call the method daemon.SetPeers to set the gubernator peers. I understood that we can bypass the configuration check by manually creating DaemonConfig . However, using the SetupDaemonConfig is much easier and has proven to work for most settings.

Therefore, with this PR, users can easily embed gubernator and manually set the peers.

@huikang huikang requested a review from Baliedge as a code owner January 8, 2025 18:44
@huikang
Copy link
Contributor Author

huikang commented Jan 8, 2025

@thrawn01 , whenever you have time, could you help review this PR? Thanks.

@thrawn01
Copy link
Collaborator

thrawn01 commented Jan 8, 2025

This is great! Thanks for making this change.

Instead of "embedded" can we call it "none" as we don't want to configure any discovery, since it will be set by your code.

@huikang
Copy link
Contributor Author

huikang commented Jan 8, 2025

This is great! Thanks for making this change.

Instead of "embedded" can we call it "none" as we don't want to configure any discovery, since it will be set by your code.

Thanks for your quick review. I like the name none. PR is updated.

@huikang huikang force-pushed the huikang/embedded-discovery-type branch from f6837cc to e882146 Compare January 8, 2025 22:45
@thrawn01 thrawn01 merged commit f885ca0 into gubernator-io:master Jan 9, 2025
4 checks passed
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.

2 participants