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

Override functionality for reactive config #10

Open
fit51 opened this issue Jan 27, 2020 · 0 comments
Open

Override functionality for reactive config #10

fit51 opened this issue Jan 27, 2020 · 0 comments
Labels
enhancement New feature or request

Comments

@fit51
Copy link
Owner

fit51 commented Jan 27, 2020

Basic Idea: one config storage can override the other.
It may be useful if your config storage doesn't support per-host configuration, but you need to override some piece of config locally. Ex. etcd.

Possible scenario

Your configuration is stored in etcd clusters that are unique per qa/prod/other environments.

  1. Though, you have some static configuration ex: hostname, unique-id, etc that apply to each app node independently...You need an ability to specify per-node configuration, and update it.
  2. Sometimes you have to override some general configuration to run tests on part of an application traffic. So, you override config on specific nodes locally.
@fit51 fit51 added the enhancement New feature or request label Jan 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant