Repository: exasol/integration-test-docker-environment (language: python)

Issue:
Update Poetry version

Update Poetry version



Discussion / hints:

Fix patch:
diff --git a/.github/workflows/check_setup_py.yaml b/.github/workflows/check_setup_py.yaml
index 4693bf784..fc16024a0 100644
--- a/.github/workflows/check_setup_py.yaml
+++ b/.github/workflows/check_setup_py.yaml
@@ -12,13 +12,13 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
-    - uses: actions/checkout@v2
+    - uses: actions/checkout@v3
     - uses: actions/setup-python@v2
       with:
         python-version: ${{ matrix.python-version }}
-    - uses: abatilo/actions-poetry@v2.1.4
+    - uses: abatilo/actions-poetry@v2
       with:
-        poetry-version: 1.1.11
+        poetry-version: 1.2.0
     - name: Run packaging update
       run: bash githooks/update_packaging.sh
     - name: Show changes on working copy
diff --git a/.github/workflows/check_version.yaml b/.github/workflows/check_version.yaml
index 3dc9e128a..8bb9829ca 100644
--- a/.github/workflows/check_version.yaml
+++ b/.github/workflows/check_version.yaml
@@ -6,7 +6,7 @@ jobs:
   check-version-numbers:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v2
+      - uses: actions/checkout@v3
         with:
           fetch-depth: 0
       - name: Setup Python 3.8
@@ -15,9 +15,9 @@ jobs:
           python-version: 3.8
 
       - name: Install Poetry
-        uses: abatilo/actions-poetry@v2.1.4
+        uses: abatilo/actions-poetry@v2
         with:
-          poetry-version: 1.1.11
+          poetry-version: 1.2.0
 
       - name: Check Release
         run: ./scripts/build/check_release.sh
diff --git a/.github/workflows/publish_docker_runner.yml b/.github/workflows/publish_docker_runner.yml
index 8d907be3d..77f1c4140 100644
--- a/.github/workflows/publish_docker_runner.yml
+++ b/.github/workflows/publish_docker_runner.yml
@@ -11,7 +11,7 @@ jobs:
     runs-on: ubuntu-latest
     environment: publish
     steps:
-    - uses: actions/checkout@v2
+    - uses: actions/checkout@v3
     - name: Build new Docker image
       run: bash ./starter_scripts/build_docker_runner_image.sh
     - name: Docker login
@@ -32,7 +32,7 @@ jobs:
     runs-on: ubuntu-latest
     environment: publish
     steps:
-      - uses: actions/checkout@v2
+      - uses: actions/checkout@v3
       - name: Build TestContainer
         run: ./start-test-env build-test-container --force-rebuild
       - name: Push TestContainer image
diff --git a/.github/workflows/release_droid_upload_github_release_assets.yml b/.github/workflows/release_droid_upload_github_release_assets.yml
index 46eafc8ce..61dd4c338 100644
--- a/.github/workflows/release_droid_upload_github_release_assets.yml
+++ b/.github/workflows/release_droid_upload_github_release_assets.yml
@@ -11,7 +11,7 @@ jobs:
   check-release:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v2
+      - uses: actions/checkout@v3
         with:
           fetch-depth: 0
 
@@ -21,9 +21,9 @@ jobs:
           python-version: 3.8
 
       - name: Install Poetry
-        uses: abatilo/actions-poetry@v2.1.4
+        uses: abatilo/actions-poetry@v2
         with:
-          poetry-version: 1.1.11
+          poetry-version: 1.2.0
 
       - name: Check Release
         run: ./scripts/build/check_release.sh
@@ -31,7 +31,7 @@ jobs:
   test-docker-starter:
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
+    - uses: actions/checkout@v3
 
     - name: Build new Docker image
       run: bash ./starter_scripts/build_docker_runner_image.sh
@@ -43,7 +43,7 @@ jobs:
     needs: [test-docker-starter, check-release]
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
+    - uses: actions/checkout@v3
 
     - name: Setup Python 3.8
       uses: actions/setup-python@v2
@@ -51,9 +51,9 @@ jobs:
         python-version: 3.8
 
     - name: Install Poetry
-      uses: abatilo/actions-poetry@v2.0.0
+      uses: abatilo/actions-poetry@v2
       with:
-        poetry-version: 1.1.11
+        poetry-version: 1.2.0
 
     - name: Build Release
       run: |
diff --git a/.github/workflows/shellcheck.yaml b/.github/workflows/shellcheck.yaml
index 019ff3e3b..30bc9738d 100644
--- a/.github/workflows/shellcheck.yaml
+++ b/.github/workflows/shellcheck.yaml
@@ -6,6 +6,6 @@ jobs:
   shellcheck:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v2
+      - uses: actions/checkout@v3
       - name: Run shellcheck
         run: ./scripts/build/shellcheck.sh
diff --git a/doc/changes/changes_0.12.0.md b/doc/changes/changes_0.12.0.md
index 0ddef081a..cee7b27d5 100644
--- a/doc/changes/changes_0.12.0.md
+++ b/doc/changes/changes_0.12.0.md
@@ -33,6 +33,7 @@ TBD
 
 - #235: Moved implementations of all click commands in separate methods
 - #240: Created more integation tests for api calls and implemented return values
+- #251: Updated Poetry
 
 ## Documentation:
 - TBD
diff --git a/setup.py b/setup.py
index a976fb0c7..a7199aa0f 100644
--- a/setup.py
+++ b/setup.py
@@ -89,8 +89,8 @@
     'long_description': '# Integration Test Docker Environment\n\n## About\n\nThis project provides a command line interface to start a test environment with an [Exasol Docker-DB](https://hub.docker.com/r/exasol/docker-db). It starts an Exasol Docker-DB container and an associated test container where [EXAPlus CLI](https://docs.exasol.com/connect_exasol/sql_clients/exaplus_cli/exaplus_cli.htm) and  the [Exasol ODBC driver](https://docs.exasol.com/connect_exasol/drivers/odbc.htm) are already installed.\n\nBoth containers exist in the same Docker network. This allows you to connect from the test container to the Docker-DB container. Furthermore, the database gets populated with some test data. You can find the test data under `tests/test/enginedb_small/import.sql`. Besides the test container, you can also access the Exasol database and the Bucket-FS from the host via forwarded ports.\n\n### Comparison to Docker-DB and the Exasol Testcontainers\n\n* This project uses the [Docker-DB](https://hub.docker.com/r/exasol/docker-db), but it does the configuration, setup and startup for you. For example, it waits until the Database and the Bucket-FS accept connections. It also populates the database with test data and provides with the test container as an environment to access the database.\n* The [Exasol Testcontainers](https://github.com/exasol/exasol-testcontainers/) provide similar features for Java integration tests, so if you have an Java project use the Exasol Testcontainer, because they are more integrated in the Java ecosystem then this project. Testcontainers are designed to integrate with popular unit testing frameworks like [JUnit4](https://www.testcontainers.org/test_framework_integration/junit_4/), [JUnit5](https://www.testcontainers.org/test_framework_integration/junit_5/) and [Spock](https://www.testcontainers.org/test_framework_integration/spock/). Most notably, lifecycle management of containers controlled by the tests lifecycle.\n\nHowever, if you have a project in any other language you can use this project to start a test Exasol database via a command line interface.\n\n## Prerequisites\n\nIn order to start a Docker-DB Test Environment, you need:\n\n* Tested Operating System:\n  * Linux\n  * Mac OS X with [Docker Desktop on Mac](https://docs.docker.com/docker-for-mac/install/) and Intel processor\n  * Windows is currently **not supported**\n* Docker with privileged mode\n* At least 2 GiB RAM\n* We recommend at least 15 GB free disk space on the partition \n  where Docker stores its images and containers. On Linux Docker typically stores \n  the images under `/var/lib/docker`.\n\n## Getting started\n\nClone the repository\n\n```\ngit clone https://github.com/exasol/integration-test-docker-environment\n```\n\nStarting the test environment:\n\n```\n./start-test-env spawn-test-environment --environment-name <NAME>\n```\nor if you work on the code of the Test Environment (requires Python >=3.8 with [poetry](https://python-poetry.org/)):\n\n```\n./start-test-env-with-poetry spawn-test-environment --environment-name <NAME>\n```\n\nShutdown of the test environment is currently done manual.\n\n### Options\n\nThe following options are available to customize the test environment. \n\n```\nUsage: main.py spawn-test-environment [OPTIONS]\n\n  This command spawn a test environment with a docker-db container and a\n  connected test-container. The test-container is reachable by the database\n  for output redirects of UDFs.\n\nOptions:\n  --environment-name TEXT         Name of the docker environment. This name\n                                  gets used as suffix for the container\n                                  db_container_<name> and\n                                  test_container_<name>  [required]\n\n  --database-port-forward INTEGER\n                                  Host port to which the database port gets\n                                  forwarded\n\n  --bucketfs-port-forward INTEGER\n                                  Host port to which the BucketFS port gets\n                                  forwarded\n\n  --db-mem-size TEXT              The main memory used by the database. Format\n                                  <number> <unit>, e.g. 1 GiB. The minimum\n                                  size is 1 GB, below that the database will\n                                  not start.  [default: 2 GiB]\n\n  --db-disk-size TEXT             The disk size available for the database.\n                                  Format <number> <unit>, e.g. 1 GiB. The\n                                  minimum size is 100 MiB. However, the setup\n                                  creates volume files with at least 2 GB\n                                  larger size, because the database needs at\n                                  least so much more disk.  [default: 2 GiB]\n\n  --nameserver TEXT               Add a nameserver to the list of DNS\n                                  nameservers which the docker-db should use\n                                  for resolving domain names. You can repeat\n                                  this option to add further nameservers.\n\n  --deactivate-database-setup / --no-deactivate-database-setup\n                                  Deactivates the setup of the spawned\n                                  database, this means no data get populated\n                                  and no JDBC drivers get uploaded. This can\n                                  be used either to save time or as a\n                                  workaround for MacOSX where the\n                                  test_container seems not to be able to\n                                  access the tests directory  [default: False]\n\n  --docker-runtime TEXT           The docker runtime used to start all\n                                  containers\n\n  --docker-db-image-version TEXT  Docker DB Image Version against which the\n                                  tests should run.  [default: 7.1.12]\n\n  --docker-db-image-name TEXT     Docker DB Image Name against which the tests\n                                  should run.  [default: exasol/docker-db]\n\n  --output-directory DIRECTORY    Output directory where the system stores all\n                                  output and log files.  [default:\n                                  .build_output]\n\n  --temporary-base-directory DIRECTORY\n                                  Directory where the system creates temporary\n                                  directories.  [default: /tmp]\n```\n\nYou can look at them on the commandline with:\n\n```\n./start-test-env spawn-test-environment --help \n```\n\n### The integration-test-docker-environment command line tool\nBesides, the already mentioned command `spawn-test-environment`, the integration-test-docker-environemnt\ncommand line tool provides a couple of other helpful tools.\n\nRun `main.py --help`, to get a list of the available commands:\n```console\nUsage: main.py [OPTIONS] COMMAND [ARGS]...\n\nOptions:\n  --help  Show this message and exit.\n\nCommands:\n  build-test-container    This command builds all stages of the test...\n  health                  Check the health of the execution environment.\n  push-test-container     This command pushs all stages of the test...\n  spawn-test-environment  This command spawn a test environment with a...\n```\n\nTo get more details on a specific command run `main.py <command> --help`,\ne.g. `main.py health --help`:\n\n```console\nUsage: main.py health [OPTIONS]\n\n  Check the health of the execution environment.\n\n  If no issues have been found, using the library or executing the test should\n  work just fine. For all found issues there will be a proposed fix/solution.\n\n  If the environment was found to be healthy the exit code will be 0.\n\nOptions:\n  --help  Show this message and exit.\n```\n\n### Default Credentials\n\nThe default credentials for the database are\n\n  * User: `sys`\n  * Password: `exasol`\n  \nand for the Bucket-FS:\n\n  * User: `w`\n  * Password: `write`\n  \nor\n\n  * User: `r`\n  * Password: `read`\n\n### Accessing the Environment Information\n\nThe python setup script creates configuration files on the host and in the test container.\n\nOn the host the container information get stored in the build output directory usually under `.build_output/cache/<ENVIRONMENT_NAME>/*`. In the test container the config file is stored at the root directory `/`.\n\nThe following config files are available:\n\n- environment_info.sh: This file is meant to be source by the bash and then provides the information as environment variables. Here an example for the content:\n\n  ```\n  export ENVIRONMENT_NAME=test\n  export ENVIRONMENT_TYPE=EnvironmentType.docker_db\n\n  # Database IP in environment docker network\n  export ENVIRONMENT_DATABASE_HOST=172.21.0.2\n  export ENVIRONMENT_DATABASE_DB_PORT=8888\n  export ENVIRONMENT_DATABASE_BUCKETFS_PORT=6583\n  export ENVIRONMENT_DATABASE_CONTAINER_NAME=db_container_test\n  export ENVIRONMENT_DATABASE_CONTAINER_NETWORK_ALIASES="exasol_test_database db_container_test"\n  # Database IP in the environment docker network\n  export ENVIRONMENT_DATABASE_CONTAINER_IP_ADDRESS=172.21.0.2\n  export ENVIRONMENT_DATABASE_CONTAINER_VOLUMNE_NAME=db_container_test_volume\n  # Database IP on the docker default bridge which under Linux available from the host\n  export ENVIRONMENT_DATABASE_CONTAINER_DEFAULT_BRIDGE_IP_ADDRESS=172.17.0.3\n\n  export ENVIRONMENT_TEST_CONTAINER_NAME=test_container_test\n  export ENVIRONMENT_TEST_CONTAINER_NETWORK_ALIASES="test_container test_container_test"\n  # Test Container IP in the environment docker network\n  export ENVIRONMENT_TEST_CONTAINER_IP_ADDRESS=172.21.0.3\n  ```\n- environment_info.json: Contains the EnvironmentInfo objects pickled with JsonPickle\n  \n### Currently supported Exasol Versions\n\n* **7.0**: up to 7.0.19 **except 7.0.5**\n* **7.1**: up to 7.1.12\n\n\nIf you need further versions, please open an issue.\n\n### Tested Docker Runtimes\n\n- Docker Default Runtime\n- [NVIDIA Container Runtime](https://github.com/NVIDIA/nvidia-container-runtime) for GPU accelerated UDFs\n\n## Mac OS X Support\n\n### What do I need to do to start the Test Environment with Mac OS X\n\nThe Exasol Docker-DB needs per default a bit more than 2 GB of RAM, however the Docker VM on Mac OS X provides often not enough RAM to accommodate this. You should increase the RAM of the Docker VM to at least 4.25 GB or reduce the DB Mem Size for the Exasol Docker-DB to less than 2 GB with `--db-mem-size 1 GiB`.\n\n### What happens under the hood\n\nMac OS X with Docker Desktop for Mac uses a lightweight virtual machine with linux in which the docker daemon runs and the containers get started. This makes [networking](https://docs.docker.com/docker-for-mac/networking/) and [shared directories](https://docs.docker.com/docker-for-mac/osxfs/) more complicated then on Linux.\n\nWe start the python setup script for the test environment in its own Docker container, lets call it `docker runner`, because the library [Luigi](https://luigi.readthedocs.io/en/stable/) can have problems with Mac OS X and to avoid the installation of further dependencies. To support Mac OS X, the `start-test-env` script starts the `docker runner` container and mounts the docker socket at `/var/run/docker.sock` and the directory of the test environment from the Mac OS X host to the container. Then, it starts `start-test-env-without-docker` which then starts the python script. It is important, that the repository gets cloned to the Mac OS X host and not to a docker container, because the python scripts tries to start further docker container which use host mounts to share the tests directory of the test environment with the docker container.\n',
     'author': 'Torsten Kilias',
     'author_email': 'torsten.kilias@exasol.com',
-    'maintainer': None,
-    'maintainer_email': None,
+    'maintainer': 'None',
+    'maintainer_email': 'None',
     'url': 'https://github.com/exasol/integration-test-docker-environment',
     'packages': packages,
     'package_data': package_data,
diff --git a/starter_scripts/checksums/poetry_utils.sh.sha512sum b/starter_scripts/checksums/poetry_utils.sh.sha512sum
index 867752c09..cdbd202e0 100644
--- a/starter_scripts/checksums/poetry_utils.sh.sha512sum
+++ b/starter_scripts/checksums/poetry_utils.sh.sha512sum
@@ -1,1 +1,1 @@
-9d3ca581906934bcf6ea37bb409495781ba17f8a95b4d411c8da86b53cca862f77bba1a858709a02a90929bdc50acef98a5964a5a068764e09f237782d705eaf  poetry_utils.sh
+0bfef760f40ec4ed3234a17d82d0368f25304e04c83ee4f3fab13cc806ca25cc6bb4b06b6f90fae23c2e2ee5edb1cefcfdee2eb67acc58ce05c0df0c9f2d217b  poetry_utils.sh
diff --git a/starter_scripts/poetry_utils.sh b/starter_scripts/poetry_utils.sh
index fb469879a..5769325ff 100644
--- a/starter_scripts/poetry_utils.sh
+++ b/starter_scripts/poetry_utils.sh
@@ -9,8 +9,7 @@ init_poetry() {
 
 request_install_poetry() {
   install_command="cat get-poetry.py | python3 -"
-  curl -sSL -o get-poetry.py https://raw.githubusercontent.com/python-poetry/poetry/master/get-poetry.py
-  sed -i 's/allowed_executables = \["python", "python3"\]/allowed_executables = ["python3", "python"]/' get-poetry.py
+  curl -sSL -o get-poetry.py https://install.python-poetry.org
   if [ "$POETRY_INSTALL" = YES ]; then
     ANSWER=yes
   else


Test patch:
diff --git a/.github/workflows/test_db_versions_all_tests.yml b/.github/workflows/test_db_versions_all_tests.yml
index 58d136f7b..48bebcc3a 100644
--- a/.github/workflows/test_db_versions_all_tests.yml
+++ b/.github/workflows/test_db_versions_all_tests.yml
@@ -10,7 +10,7 @@ jobs:
   get_exasol_versions:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v2
+      - uses: actions/checkout@v3
       - name: Install jq
         run: sudo apt-get install jq
       - name: Print matrix
@@ -30,16 +30,16 @@ jobs:
     runs-on: ubuntu-latest
     name: Run all tests for Exasol ${{ matrix.exasol_version }}
     steps:
-    - uses: actions/checkout@v2
+    - uses: actions/checkout@v3
 
     - name: Setup Python 3.8 for integration-test-docker-environment
       uses: actions/setup-python@v2
       with:
         python-version: 3.8
     - name: Install Poetry
-      uses: abatilo/actions-poetry@v2.1.4
+      uses: abatilo/actions-poetry@v2
       with:
-        poetry-version: 1.1.11
+        poetry-version: 1.2.0
 
     - name: Fail, because not all tests are activated
       run: |
diff --git a/.github/workflows/test_db_versions_minimal.yml b/.github/workflows/test_db_versions_minimal.yml
index ff060c082..d5eb87a44 100644
--- a/.github/workflows/test_db_versions_minimal.yml
+++ b/.github/workflows/test_db_versions_minimal.yml
@@ -11,7 +11,7 @@ jobs:
   get_exasol_versions:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v2
+      - uses: actions/checkout@v3
       - name: Install jq
         run: sudo apt-get install jq
       - name: Print matrix
@@ -31,16 +31,16 @@ jobs:
     runs-on: ubuntu-latest
     name: Run minimum tests for Exasol ${{ matrix.exasol_version }}
     steps:
-    - uses: actions/checkout@v2
+    - uses: actions/checkout@v3
 
     - name: Setup Python 3.8 for integration-test-docker-environment
       uses: actions/setup-python@v2
       with:
         python-version: 3.8
     - name: Install Poetry
-      uses: abatilo/actions-poetry@v2.1.4
+      uses: abatilo/actions-poetry@v2
       with:
-        poetry-version: 1.1.11
+        poetry-version: 1.2.0
 
     - name: Run minimal tests
       run: |
diff --git a/.github/workflows/test_docker_starter.yml b/.github/workflows/test_docker_starter.yml
index 58cf63487..932dd1ece 100644
--- a/.github/workflows/test_docker_starter.yml
+++ b/.github/workflows/test_docker_starter.yml
@@ -10,7 +10,7 @@ jobs:
   test-docker-starter:
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
+    - uses: actions/checkout@v3
 
     - name: Test ./start-test-env
       run: ./start-test-env health
diff --git a/.github/workflows/test_python_version.yml b/.github/workflows/test_python_version.yml
index 54b290312..e51d263c9 100644
--- a/.github/workflows/test_python_version.yml
+++ b/.github/workflows/test_python_version.yml
@@ -19,7 +19,7 @@ jobs:
     name: Run tests with Python ${{ matrix.python_version }} and Exasol ${{ matrix.exasol_version }}
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
+    - uses: actions/checkout@v3
 
     - name: Setup Python for integration-test-docker-environment
       uses: actions/setup-python@v2
@@ -27,9 +27,9 @@ jobs:
         python-version: "${{ matrix.python_version }}"
 
     - name: Install Poetry
-      uses: abatilo/actions-poetry@v2.1.4
+      uses: abatilo/actions-poetry@v2
       with:
-        poetry-version: 1.1.11
+        poetry-version: 1.2.0
 
     - name: Run all tests
       run: ./scripts/test/run_all_tests.sh
diff --git a/.github/workflows/test_shell_scripts.yml b/.github/workflows/test_shell_scripts.yml
index 1586e6b83..6aa60275f 100644
--- a/.github/workflows/test_shell_scripts.yml
+++ b/.github/workflows/test_shell_scripts.yml
@@ -7,7 +7,7 @@ jobs:
     name: Test Shell Scripts
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v2
+      - uses: actions/checkout@v3
 
       - name: Install Test Dependencies
         run: |