This message was deleted.

You can put it in application.groovy

@Diego Correa In Spring, you can modify beans using BeanPostProcessor at the runtime

Another option is to use the same is to use the Listener technique used in the external config plugin: https://github.com/sbglasius/external-config/blob/master/external-config/src/main/[…]y/grails/plugin/externalconfig/ExternalConfigRunListener.groovy https://github.com/sbglasius/external-config/blob/master/external-config/src/main/resources/META-INF/spring.factories I've used this technique a couple of times to integrate with eternal config servers like Azure Config, and AWS Parameter Store.

Hey Tucker! Diego followed your suggestion and got things working. It’s sweet that we can now store encrypted values in the config files and they are decrypted at the start of the app! Hope all is well!

Hey cool. I'm doing well just started working with Micronaut last month. You loose the convention over configuration, but now that I have an incentive to, I'll eventually bring that back with a side project. Other than that Micronaut has a lot of cool features and is similar enough to Grails. It's also nice having apps that start and can run integration tests in under a minute. Hope you're also doing well.

Life has been good but crazy, as always… I’ve been really wanting to incorporate Micronaut but the complexity of setting it up, especially for on-premise installations makes it a non-starter.

Hmm not aware of any setup complexity for running local, as you could run it as a jar or a docker container, other services could call it or you could put it behind nginx/Apache for SSL offloading. For config you can do something similar to what I described above with Property source loading. Although maybe there's some aspects I'm just not thinking of specific to your use cases.