I think that depends on how you use Spring. My Spring app is deployed via Kubernetes where I can configure environment variables and config files to attach to each service. All my relevant data I might normally look up through Spring is exposed in multiple ways.
— Matt Sicker > On Jan 14, 2022, at 06:06, Apache <ralph.go...@dslextreme.com> wrote: > > The answer is - it depends. Although we might consider using the properties > proposal I made in master many of the lookups should default to being enabled > or enabled under a condition. For example, the spring lookup only works when > spring boot is present. It would be stupid for it not to be enabled when it > is a spring boot app. > > Ralph > >> On Jan 13, 2022, at 8:19 PM, Matt Sicker <boa...@gmail.com> wrote: >> >> For the extra paranoid users and users who already use some other method of >> generating config files (e.g., using the ConfigurationBuilder DSL which >> already supports arbitrary Java code), it seems like a useful feature to >> make lookups an opt-in feature. What do you all think? Any splitting from >> core would need to be done for 3.x, though we can add @RequiredProperty >> annotations to StrLookup plugins in 2.x to make a similar change. >> -- >> Matt Sicker >> >