izumi.distage.framework.services.ConfigLoader
See theConfigLoader companion object
Default config resources:
${roleName}.conf
${roleName}-reference.conf
${roleName}-reference-dev.conf
application.conf
application-reference.conf
application-reference-dev.conf
common.conf
common-reference.conf
common-reference-dev.conf
NOTE: You can change default config locations by overriding make[ConfigLocation]
binding in izumi.distage.roles.RoleAppMain#roleAppBootOverrides (defaults defined in izumi.distage.roles.RoleAppBootModule)
When explicit configs are passed to the role launcher on the command-line using the -c
option, they have higher priority than all the reference configs.
Role-specific configs on the command-line (-c
option after :role
argument) override global command-line configs (-c
option given before the first :role
argument).
Example:
./launcher -c global.conf :role1 -c role1.conf :role2 -c role2.conf
Here configs will be loaded in the following order, with higher priority earlier:
- explicits:
role1.conf
,role2.conf
,global.conf
, - resources:
role1[-reference,-dev].conf
,role2[-reference,-dev].conf
, ,application[-reference,-dev].conf
,common[-reference,-dev].conf
Attributes
- See also:
- Companion:
- object
- Graph
- Supertypes
- Known subtypes
- class LocalFSImpl