Dustin, Look into Spring cloud config server, https://apereo.github.io/cas/6.1.x/configuration/Configuration-Server-Management.html, and store config in git with a branch for each environment. Spring cloud allows you to encrypt sensitive values. In tomcat's setenv.sh, or however you use to start your container, set the config server url and branch.
CATALINA_OPTS="$CATALINA_OPTS -Dspring.cloud.config.uri=https://casuser:[email protected]/casconfigserver"; CATALINA_OPTS="$CATALINA_OPTS -Dspring.cloud.config.enabled=true -Dspring.cloud.config.label=prod" Ray On Wed, 2020-01-15 at 11:39 -0800, Dustin J Luck wrote: I would like to add my cas.properties file for a standalone deployment to source control. I'd like to know if there is a way to put certain settings that would necessarily be different between our dev & prod environments someplace external to the main properties file so I don't need to maintain the common properties in multiple places. An example of one of the properties I'd like to manage this way is cas.ticket.registry.hazelcast.cluster.members. -- Ray Bon Programmer Analyst Development Services, University Systems 2507218831 | CLE 019 | [email protected]<mailto:[email protected]> I respectfully acknowledge that my place of work is located within the ancestral, traditional and unceded territory of the Songhees, Esquimalt and WSÁNEĆ Nations. -- - 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/e0bf6b02f3699daf95a97b23f3a02d0b62336094.camel%40uvic.ca.
