-
Notifications
You must be signed in to change notification settings - Fork 47
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
Rolling out bridge shouldnt regenerate config #39
Comments
Yeah, I've been having this same problem. I've been gradually tweaking the configuration of the bridge, but even if I make changes in I've been trying to think of a way to avoid regenerating the |
Right now, I think if you apply changes that only affect a bridge, OR need to restart a bridge using
kubectl rollout restart deployment matrix-bridge-twitter
for example.... it'll generate new config I think.... and the shared secrets wont be the same in the live version of synapse.I think!
If the config exists, you shouldnt just go remake it? But then how do you deal with the issue of wanting to update the other config?
The text was updated successfully, but these errors were encountered: