-
Notifications
You must be signed in to change notification settings - Fork 11
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
Phase out config server #144
Comments
For the admin application, it would be quite easy to replace the config server, using custom For the gateways, this will be much more complex, as existing gateways rely on config server to get their config, questions to be discussed:
|
We did not get rid of the config server, yet. It is still required to enable the correct functionality of the Gateways. |
The first part of this issue was solved in #158 (remove config server dependency from admin), but the gateway configs still required the config server. |
Within the scope of #162 I got rid of the remote BitBucket GitService. Web Application and Config Server exchange proxy configuration files via shared filesystem using a Docker volume instead of git. @perezdf I think it would make sense to wait until the PR for #162 is merged to continue with this issue as building on that PR would probably ease the process of phasing out the config server. |
TODO
The text was updated successfully, but these errors were encountered: