Exasol-integration-test-docker-environment

Latest version: v3.0.0

Safety actively analyzes 623642 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 5

3.0.0

Integration-Test-Docker-Environment 3.0.0, released 2024-02-22

Summary

Removed `pytest-itde` plugin.

Supported Exasol Versions

* **7.1**: up to 7.1.17
* **8**: 8.18.1

Breaking Changes

* Removed `pytest-itde` plugin See also

Users which do rely on the plugin should consider moving to the standalone [pytest-itde](https://pypi.org/project/pytest-exasol-itde/) plugin.
The related project can be found [here](https://github.com/exasol/pytest-plugins)

2.1.0

Integration-Test-Docker-Environment 2.1.0, released 2024-02-22

Summary

This release addresses dependencies updates and dependency issues.

Supported Exasol Versions

* **7.1**: up to 7.1.17
* **8**: 8.18.1

Dependencies

* Constrain docker dependency to `>= 4.0.0, < 7.0.0`, for further details see [docker/docker-py3223](https://github.com/docker/docker-py/issues/3223)

Internal

* 184: Streamlined error messages
* Added exasol-error-reporting library

2.0.0

Integration-Test-Docker-Environment 2.0.0, released 2023-08-07

Summary

Version 2.0.0 of ITDE comes with breaking changes as the public API class `DatabaseInfo` has been changed. Former separate attributes `database_port_forward`and `bucketfs_port_forward` have been replaced by a single attribute `port` set to an instance of `PortForwarding` with attributes `database`, `bucketfs`, and `ssh`.

Previous versions of the ITDE used `docker_exec` to access the Docker Container, e.g. to analyze the content of logfiles or execute some shell commands. In future versions of the Exasol Docker-DB the format of the Docker Containers might change so that `docker_exec` is no longer possible. Instead ITDE will then need to use SSH access.

The current release therefore enhances ITDE to enable to access the Docker Container via SSH. The user can select the docker access method with command line option `--db-os-access` and can specify a port number to which ITDE forwards the SSH port of the Docker Container, see User Guide.

Additionally the directory for storing the randomly generated SSH keys has been moved to `~/.cache/exasol/itde/`. By that ITDE can restrict file permissions allowing access only by the current user.

This release also removes versions 7.0.x of the Exasol database from the regular CI builds as version 8.x is already available and ITDE only supports the latest two minor versions.

Supported Exasol Versions

* **7.1**: up to 7.1.17
* **8**: 8.18.1

If you need further versions, please open an issue.

Internal

Changes

* 329: Added CLI option `--ssh-port-forward` to forward SSH port
* 343: Added SshInfo to DatabaseInfo containing user, port and path to SSH key file
* 308: Unified ports for database, BucketFS, and SSH
* 322: Added additional tests for environment variable LOG_ENV_VARIABLE_NAME
* 359: Fixed custom logging path not working if dir does not exist.
* 304: Create SSH access replacements for calls to `docker.exec_run()`
* 368: Removed versions 7.0.x of Exasol database
* 305: Replaced calls to `DockerContainer.exec_run()` to support SSH access alternatively

1.7.1

Integration-Test-Docker-Environment 1.7.1, released 2023-06-19

Summary

This release fixes the not working UDFs in Exasol Docker-DB 8.18.1.

Supported Exasol Versions

* **7.0**: up to 7.0.20, **except 7.0.5**
* **7.1**: up to 7.1.17
* **8**: 8.18.1

If you need further versions, please open an issue.

Internal

Changes

* 351: Added test for UDF with builtin Script-Language Container and fixed it for Docker-DB 8.18.1

1.7.0

Integration-Test-Docker-Environment 1.7.0, released 2023-06-15

Summary

This release added support for the Exasol Docker-DB 8.18.1. Furthermore, it adds the first features for accessing
the Docker-DB container via SSH instead of `docker exec`. This is in preparation for later Exasol Docker-DB releases,
for which you can't access the operating system of the database with `docker exec`. However, the SSH access itself
is not yet operational. Finally, this release fixes a bug in the reporting of task failures. The TaskRuntimeError
didn't show the actual task failures if not caught explicitly.

Supported Exasol Versions

* **7.0**: up to 7.0.20, **except 7.0.5**
* **7.1**: up to 7.1.17
* **8**: 8.18.1

If you need further versions, please open an issue.

Internal

Changes

* 301: Added commandline option `--db-os-access`
* 302: Added support to create an SSH key for accessing Docker Container
* 241: Renamed environment variable for test execution from `GOOGLE_CLOUD_BUILD` to `RUN_SLC_TESTS_WITHIN_CONTAINER`
* 190: Added support for the Exasol 8.0 Docker-DB prerelease version
* 326: Changed folder for SSH keys to `~/.cache/exasol/itde/`
* 303: Added authorized_keys to Docker Container for SSH access
* 337: Added Docker-DB 8.18.1
* 350: TaskRuntimeError will be raised as chained exception with all task failures.

1.6.0

Integration-Test-Docker-Environment 1.6.0, released 2023-05-12

Summary

This release fixes several bugs regarding logging, reusing of an environment and rebuilding the test container.

Supported Exasol Versions

* **7.0**: up to 7.0.20, **except 7.0.5**
* **7.1**: up to 7.1.17

If you need further versions, please open an issue.

Internal
- 297: Update release_config.yml
- 311: Add vagrant setup

Changes

- 294: Fixed that the client logging config gets overwritten
- 295: Fixed that the test_container_content parameter pollutes the logs
- 300: Fixed BucketFS uploads during reusing of an environment
- 310: Fixed that using run_task with log_level duplicates log entries
- 291: Fixed that test container gets rebuild when force_rebuild is true
- 316: Removed setup.py and updated poetry(1.4.0) in actions

Page 1 of 5

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.