Conversation
|
|
||
|
|
||
| def import_build_steps(flavor_path: Tuple[str, ...]): | ||
| # TODO Move to script-languages-container-tools: https://github.com/exasol/script-languages-container-tool/issues/268 |
There was a problem hiding this comment.
Was confused for the moment, because the framework for building the docker images is used also for the test container, but it is only about the build steps file.
There was a problem hiding this comment.
However, more correct would be probably extracting the docker images build part into a repo and the import with it
There was a problem hiding this comment.
Hm, I see that the flavor_path and and FlavorsBaseTask and so on, which are tasks specific for exaslct are also here. So I guess you are right, and it's does not make sense to move this single function only then to exaslct. I will close exasol/script-languages-container-tool#268
There was a problem hiding this comment.
However FlavorBaseTask doesn't belong here, contrary to the import build steps. Also the test env should not know about flavors, that should be added in slct
| module = [ "luigi.*", "docker.*", "humanfriendly", "configobj", "toml", "netaddr", "joblib.testing", "networkx", | ||
| "fabric", "requests", "pyexasol", "paramiko.ssh_exception", "six", "jsonpickle", "exasol.toolbox.*", | ||
| "paramiko", "exasol"] | ||
| "paramiko", "exasol", "networkx.classes"] |
There was a problem hiding this comment.
Do we still need the exasol override, if yes then the question which repo is the offender
There was a problem hiding this comment.
There was a problem hiding this comment.
2. Moved common.py -> base/import_build_step.py 3. Moved run_task.py -> base/run_task.py
| from exasol_integration_test_docker_environment.cli.cli import cli | ||
| from exasol_integration_test_docker_environment.lib import api | ||
| from exasol_integration_test_docker_environment.lib.api.api_errors import HealthProblem | ||
| from exasol_integration_test_docker_environment.lib.models.api_errors import ( |
There was a problem hiding this comment.
This looks like you might change the external interface, because moving externally used files might break imports. i have the feeling, we really need to set up a check for potential API breakage. https://github.com/StardustDL/aexpy
There was a problem hiding this comment.
Increased Major version to 4.0.0
Co-authored-by: Torsten Kilias <tkilias@users.noreply.github.com>
fixes #430
All Submissions:
Details
lib/config->lib/models/configlib/data->lib/models/datalibapi/api_errors.py->lib/models/api_errors.pylib/base/run_tasks.pylib/utils