On Tue, 21 May 2019 05:32:35 -0700 (PDT)
Andy Ng <long...@gmail.com> wrote:
> instead of cas.standalone.config=/etc/cas/config
> - bootstrap.properties load before application.properties or
> application.yml, that's why your modification didn't work
> - One way to do it (I don't know if recommended or not...)
> is to put your cas.standalone.config:
> /etc/cas/config inside *bootstrap.yml* instead
> - yml load after properties, so bootstrap.yml will override
> bootstrap.properties.
Thank you, Andy.
This worked like a charm. For anyone interested, I have now
<properties>
...
<springApplicationName>casldap1</springApplicationName>
<casStandaloneConfig>/usr/local/etc/casldap1/</casStandaloneConfig>
...
</properties>
in the <profile> section of the pom.xml, and the command
mvn -Pldap1 clean package
fills the values in my src/main/resources/bootstrap.yml, which reads
cas:
standalone:
config : ${casStandaloneConfig}
spring:
application:
name : ${springApplicationName}
> I also agrees that using config is the sometime the better option,
> especially when you already have a system to manage config files,
> just didn't see the benefit of switching to spring config.
Sure, I'll look into spring config, but at this stage I'm just
trying to avoid brain overload.
Thank you very much again,
--
Alberto Cabello Sánchez
Servicio de Informática
Universidad de Extremadura
--
- 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 cas-user+unsubscr...@apereo.org.
To view this discussion on the web visit
https://groups.google.com/a/apereo.org/d/msgid/cas-user/20190523124839.1201c5600ca0dde6ae5b8b2c%40unex.es.
