So I'm planning to jump right over CAS 4.x and take advantage of all the CAS 5.0 awesomeness (we're part of the 53% still running 3.5.2). Just for a change of pace, I thought I'd try actually reading all the instructions first this time and planning things out, instead of just jumping into "mvn clean package" and figuring it out as I go :-). And I must say, the new documentation site is excellent. So far it's been super-easy to find my way around and read about the things I want to know, and the linking from the top-level pages to the lower-level detail pages is really easy to follow. Combined with all the work you've done on intention-driven configuration, I'm enjoying the process of planning my CAS 5.0 deployment so much more than I did when I was working on CAS 3.x.
But, I have come up with a couple of questions... At the bottom of the "Configuration Management" page (https://apereo.github.io/cas/development/installation/Configuration-Management.html) there are a couple of sections, "Reloading Changes" and "Clustered Deployments" that I'm not sure I completely understand. First, reloading changes. The first paragraph there explains the embedded configuration server that notices when the application.properties file gets updated and reloads the properties. But then the second paragraph talks about an "adopter" needing to submit a request to CAS to refresh its current state to make the new properties actually take effect. But it doesn't say whether the embedded configuration server is considered an adopter. So here's my first point of confusion -- If I edit application.properties, will those changes take effect all by themselves just by editing the file? Or do I also need to manually visit the server dashboard page and click "Refresh"? Next, clustered deployments. I understand that if the Spring Cloud Bus is configured, then when one of the servers reloads its properties, it will broadcast them out to the other servers on the bus, so that they all get them. But here's my next point of confusion -- Let's suppose I have 3 servers (A, B, and C) and change the properties file on A. The Cloud Bus will make sure those changes get propagated to the running instances on B and C, but will it also update the properties file on those two servers? Or do I need to make sure the files are kept in sync through some out-of-band process? Thanks, --Dave -- 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 post to this group, send email to [email protected]. Visit this group at https://groups.google.com/a/apereo.org/group/cas-user/. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/2148dba1-c059-4c45-babe-4e6c48144924%40apereo.org. For more options, visit https://groups.google.com/a/apereo.org/d/optout.
