search

exasol / integration-test-docker-environment

A docker-based environment for integration tests with the EXASOL DB.
https://exasol.github.io/integration-test-docker-environment/
MIT License
6 stars 2 forks source link

Add CLI command to cleanup all parts of an environment #24

Closed tkilias closed 1 week ago

tkilias commented 4 years ago

Situation:

Currently, the user needs to manually clean up the environment after the usage. The manual cleanup requires the extraction of names of the docker resources from the configs and then issuing manual docker commands to remove them.

Todo:

Add a CLI command which automatically removes all docker resources associated to an environment name.

Remarks:

We already have a way to remove the environment when the setup fails via the cleanup methods of the corresponding Spawn-Tasks. The question is, can we reuse it. It is probably a good idea to use the cleanup methods because then creation and cleanup are near together in the code which makes it easier to keep them in sync. The main issue with this is probably, that some of the Spawn-Tasks only get created during the runtime and during the task graph construction. We may be able to work around it, by extracting the cleanup methods from the dynamically created Spawn-Tasks.

ckunki commented 1 year ago

What are the differences to ticket #109?

ckunki commented 1 year ago

Hello @tkilias: Could you please elaborate the following tickets and make clear differences and relationships, e.g. dependencies: