Background
Eclipse Kanto Container Management recently implemented the automated initial deployment of containers based on json manifests. Integrators can define the "init_dirs" configuration property and kanto-cm will take care of creating and starting the containers when the service starts.
Initially, kanto-auto-deployer (KAD) in leda-utils was meant to be that feature. Now, it became obsolete. But we can implement more convenient features in KAD which will probably not be implemented in kanto-cm (as they're not for production use), to make reuse of the code.
File change watchdog
Whenever a json manifest changes on disk (e.g. newly created, or touched/updated), KAD will delete the corresponding container and recreate it with the new settings. These will for example allow to add or change environment variables for a containerized process and KAD can automatically recreate the container. Kanto-cm would not pick up these changes, as in a production environment, such manual file changes are not be expected.
Note: For framing this idea, other features for KAD may be: auto-delete duplicate containers based on name, import container images from filesystem for offline installation ("AirGap")
Background Eclipse Kanto Container Management recently implemented the automated initial deployment of containers based on json manifests. Integrators can define the "init_dirs" configuration property and kanto-cm will take care of creating and starting the containers when the service starts.
Initially, kanto-auto-deployer (KAD) in leda-utils was meant to be that feature. Now, it became obsolete. But we can implement more convenient features in KAD which will probably not be implemented in kanto-cm (as they're not for production use), to make reuse of the code.
File change watchdog Whenever a json manifest changes on disk (e.g. newly created, or touched/updated), KAD will delete the corresponding container and recreate it with the new settings. These will for example allow to add or change environment variables for a containerized process and KAD can automatically recreate the container. Kanto-cm would not pick up these changes, as in a production environment, such manual file changes are not be expected.
Note: For framing this idea, other features for KAD may be: auto-delete duplicate containers based on name, import container images from filesystem for offline installation ("AirGap")