augustearth
commented
4 years ago This is sort-of not a thing... Yaml allows us to combine Carnival config stuff with app config stuff. Micronaut apps prove that. I think we're ok here for now... not that the question of Defaults.groovy has gone away. There is probably a way to clean things up so they make more sense.
For applications that have their own configuration machinery, it would be nice not to require a separate configuration file for Carnival configuration. Figure out how to provide the config data to Carnival directly so no separate file is required.
Scope carnival configuration within a top level element, which would enable integration of a carnival configuration in an existing application.yaml file that includes other application configuration.