Overriding properties from idp.properties at deploy time

[John C. Pfeifer]

I am running a container based on the InCommon Trusted Access (formerly TIER) docker container. I have added a tree, /environements/<env>/…, that mirrors the IdP tree and contains things that should be specific to the given environment (certs, idp metadata, properties, messages, etc.) which is overlayed onto /opt/shbboleth-idp by our container startup script (which then calls the startup script of the base image). The <env> is set from a shell variable that is passed into the container.

//
John Pfeifer
Division of Information Technology
University of Maryland, College Park

> On May 4, 2022, at 2:17 PM, Russell Jackson via users <users at shibboleth.net> wrote:
> 
> To facilitate deploying the same container image in different deployment scenarios, it would be convenient to supply defaults in idp.properties but then be able to generate a local overrides file at deploy time to override specific properties.
>  
> This used to work on the 3.x branch by listing it (e.g. /conf/overrides.properties) last in idp.additionalProperties; however, 4.x seems to follow a first assignment wins strategy. I've been able to get around it by just not having defaults, but the previous behavior sure was handy.
>  
> -- 
> Russell Jackson
> California State University, San Bernardino
> -- 
> For Consortium Member technical support, see https://shibboleth.atlassian.net/wiki/x/ZYEpPw <https://shibboleth.atlassian.net/wiki/x/ZYEpPw>
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net <mailto:users-unsubscribe at shibboleth.net>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20220505/937bb1e8/attachment.htm>