-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create SSH access replacements for calls to docker.exec_run() #362
Create SSH access replacements for calls to docker.exec_run() #362
Conversation
incl. unit tests
ported test_upload.py to pytest fixed test container names for parameterized tests
parameterized test_db_available()
…or_calls_to_docker.exec_run # Conflicts: # doc/changes/changes_2.0.0.md
exasol_integration_test_docker_environment/lib/base/db_os_executor.py
Outdated
Show resolved
Hide resolved
exasol_integration_test_docker_environment/lib/base/db_os_executor.py
Outdated
Show resolved
Hide resolved
exasol_integration_test_docker_environment/lib/base/db_os_executor.py
Outdated
Show resolved
Hide resolved
exasol_integration_test_docker_environment/lib/base/db_os_executor.py
Outdated
Show resolved
Hide resolved
exasol_integration_test_docker_environment/lib/base/db_os_executor.py
Outdated
Show resolved
Hide resolved
exasol_integration_test_docker_environment/lib/base/db_os_executor.py
Outdated
Show resolved
Hide resolved
Co-authored-by: Torsten Kilias <[email protected]>
exasol_integration_test_docker_environment/lib/base/db_os_executor.py
Outdated
Show resolved
Hide resolved
Moved instanciate DockerClient to DockerExecFactory.executor() Replaced interface DockerClientFactory by implementation based on ContextDockerClientFactory
exasol_integration_test_docker_environment/lib/base/db_os_executor.py
Outdated
Show resolved
Hide resolved
exasol_integration_test_docker_environment/lib/base/db_os_executor.py
Outdated
Show resolved
Hide resolved
exasol_integration_test_docker_environment/lib/base/db_os_executor.py
Outdated
Show resolved
Hide resolved
...r_environment/lib/test_environment/database_setup/docker_db_log_based_bucket_sync_checker.py
Show resolved
Hide resolved
..._test_docker_environment/lib/test_environment/database_setup/find_exaplus_in_db_container.py
Outdated
Show resolved
Hide resolved
..._test_docker_environment/lib/test_environment/database_setup/find_exaplus_in_db_container.py
Show resolved
Hide resolved
...r_environment/lib/test_environment/database_setup/docker_db_log_based_bucket_sync_checker.py
Outdated
Show resolved
Hide resolved
Co-authored-by: Torsten Kilias <[email protected]>
…_docker.exec_run' of https://github.com/exasol/integration-test-docker-environment into feature/304-Create_SSH_access_replacements_for_calls_to_docker.exec_run
…ation-test-docker-environment into feature/304_fix_tk # Conflicts: # exasol_integration_test_docker_environment/lib/base/db_os_executor.py
3731749
to
0748dbb
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't see, if we have a integration test for the executor which only run these
exasol_integration_test_docker_environment/lib/base/db_os_executor.py
Outdated
Show resolved
Hide resolved
exasol_integration_test_docker_environment/lib/base/db_os_executor.py
Outdated
Show resolved
Hide resolved
exasol_integration_test_docker_environment/lib/base/db_os_executor.py
Outdated
Show resolved
Hide resolved
exasol_integration_test_docker_environment/lib/base/db_os_executor.py
Outdated
Show resolved
Hide resolved
exasol_integration_test_docker_environment/lib/base/db_os_executor.py
Outdated
Show resolved
Hide resolved
...ion_test_docker_environment/lib/test_environment/database_waiters/db_container_log_thread.py
Show resolved
Hide resolved
...on_test_docker_environment/lib/test_environment/database_waiters/is_database_ready_thread.py
Outdated
Show resolved
Hide resolved
...on_test_docker_environment/lib/test_environment/database_waiters/is_database_ready_thread.py
Outdated
Show resolved
Hide resolved
...on_test_docker_environment/lib/test_environment/database_waiters/is_database_ready_thread.py
Show resolved
Hide resolved
...ration_test_docker_environment/lib/test_environment/spawn_test_environment_with_docker_db.py
Show resolved
Hide resolved
Co-authored-by: Torsten Kilias <[email protected]>
…_docker.exec_run' of https://github.com/exasol/integration-test-docker-environment into feature/304-Create_SSH_access_replacements_for_calls_to_docker.exec_run # Conflicts: # exasol_integration_test_docker_environment/lib/base/db_os_executor.py
I (again) admire your razor 🔪 eyes. 👀 We have
Up to now we do not have a dedicated integration test for executors and factories ... ... but we have parameterized tests in test/integration/test_bucketfs_upload.py which will cover full integration tests involving executors and factories as well, as soon as the implementation will be updated to actually use them. This is planned in ticket #305. So if I can convince you to follow my explanation we could go this way. Otherwise it would not bee too much effort to add dedicated integration tests for executors and factories. The only downside would be some additional runtime required in the CI build. |
Hm, I am thinking about, if we can make these integration tests cheaper. In the sense, do we really need a database to test this functionality. I think, any ssh capable docker container should work. |
OK: As aligned:
client.images.pull("panubo/sshd", tag="1.1.0")
container = client.containers.run(
name="ssshd",
image="linuxserver/openssh-server:9.3_p2-r0-ls123",
environment=[...]) Appropriate environment variables (see documentation on docker hub):
|
Closes #304
All Submissions:
[run all tests]
to the commit message