Type Members

1.  trait AbstractConfigLoader extends AnyRef
2.  trait ActivationChoicesExtractor extends AnyRef
3.  class BootstrapPlatformModule extends BootstrapModuleDef
4.  trait ConfigArgsProvider extends AnyRef
5.  trait ConfigFilteringStrategy extends AnyRef
6.  trait ConfigLoader extends AbstractConfigLoader

   Default config resources:

   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[ConfigLocationProvider] 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

   See also

   ConfigLocationProvider

   ConfigLoader.LocalFSImpl

7.  trait ConfigLocationProvider extends AnyRef
8.  trait ConfigMerger extends AnyRef
9.  trait ModuleProvider extends AnyRef

   This component is responsible for passing-through selected components from the outer izumi.distage.roles.RoleAppBootModule context into DI scope of the started application.

   This component is responsible for passing-through selected components from the outer izumi.distage.roles.RoleAppBootModule context into DI scope of the started application.

   The application doesn't outright inherit the outer context because that would bring in way too many unrelated components into scope.

   This will also add some other useful components:

   • GraphViz dump hook will be enabled if PlanningOptions#addGraphVizDump is enabled (via --debug-dump-graph commandline parameter)
   • IzLogger will be passed in from the outer context
   • LogIO[F] will be available with the application's effect type
   • LocatorRef @Id("roleapp") allows accessing components from outer context if needed

   See also

   GraphViz Rendering

10.  class PlanCircularDependencyCheck extends AnyRef
11.  class ResourceRewriter extends PlanningHook

    Rewrites bindings implemented with _ <: AutoCloseable into resource bindings that automatically close the implementation closeable.

    Rewrites bindings implemented with _ <: AutoCloseable into resource bindings that automatically close the implementation closeable.

    class XImpl extends AutoCloseable
    make[X].from[XImpl]

    becomes:

    make[X].fromResource {
     ClassConstructor[XImpl].map(distage.Lifecycle.fromAutoCloseable(_))
    }

    Will produce warnings for all rewritten bindings, so better explicitly use .fromResource!

12.  trait RoleAppPlanner extends AnyRef