Overriding properties from idp.properties at deploy time

[Cantor, Scott]

>    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.

It was not a defined behavior.

It *may* work consistently if you turn off auto-lookup of files and explicitly specify them like before. If that works, then it does in fact override them via load order and I think that will be true going forward.

But I wouldn't. If you want to manage everything yourself in one place, empty out all the other files, put everything you want into idp.properties and do it that way. There are no requirements for any specific named files except that one file that is the root of the process, and as long as they exist empty, upgrades won't populate any content into them. It's purely style/peference whether to have one or many, choose as you prefer.

I do think that it's also possibly the case that env trumps the files. If that works, you can just manage it via an externally imposed set of variables, so the same as you wanted but in a different place.

-- Scott