Hello, I’ve tried a few different configurations with the new services-repo and hazelcast. I have two nodes N1 and N2 both have been configured in two ways:
The first way: for both nodes mgmt.versionControl.servicesRepo=/etc/cas/services-repo cas.serviceRegistry.json.location=file:/etc/cas/config/services The management web interface deletes the service from /etc/cas/services-repo and does not remove it from /etc/cas/config/services/ and hazelcast will not propagate the changes. Edits and Adds work, just not deletes. The second way: for both nodes mgmt.versionControl.servicesRepo=/etc/cas/services-repo cas.serviceRegistry.json.location=file:/etc/cas/services-repo then Edits,Adds and DELETES work properly. However, if I am on N1 and I commit and publish changes the versionControl on N2 dutifully picks up the changes. So when I am on N2 in the management interface I have to commit and publish the changes. Please tell me If I’m missing a setting somewhere… Thanks, Erik Mallory Server Analyst Wichita State University -- - Website: https://apereo.github.io/cas - Gitter Chatroom: https://gitter.im/apereo/cas - List Guidelines: https://goo.gl/1VRrw7 - Contributions: https://goo.gl/mh7qDG --- You received this message because you are subscribed to the Google Groups "CAS Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/47BC6362-BAE6-4472-A759-621231A6BAB2%40wichita.edu.
