search

exasol / script-languages-release

Release Repository for Script Language Container for user defined functions (UDF's) that can be used in the EXASOL database.
https://docs.exasol.com/database_concepts/udf_scripts.htm
GNU General Public License v3.0
9 stars 5 forks source link

Add version information to slc #751

Open tomuben opened 1 year ago

tomuben commented 1 year ago

Background

Currently, the only way to discover the version of a (pre-)installed SLC is to search for the SLC directory in the (default) BucketFS.

The slc connection string for the preinstalled SLC, which can be found in the database system tables, is like:

PYTHON=builtin_python R=builtin_r JAVA=builtin_java PYTHON3=builtin_python3

-> It does not contain any useful information.

We should somehow store the version information when creating a release SLC under /build_info and optionally provide an UDF in exa-toolbox which prints the version stored under /build_info.

Acceptance Criteria

Under discussion

  1. Extend docker_build task with new parameter version, which then will be copied to /build_info
  2. Adjust script-languages-container-ci to forward the version info to build and release.
tkilias commented 1 year ago

We already have the option build_name in the build command of the SLCs. https://github.com/exasol/script-languages-container-tool/blob/8aa7493f9b8a17a293790d638148a4a62887c249/exasol_script_languages_container_tool/cli/commands/build.py

The main issue is that we need to set this parameter in the AWS CodeBuild Release Workflow with the correct version of the SLCs. This version is available via the pyproject.toml of the SLC repo. However, we need to provide the package name to the slc-ci, because if we split the slc repo this name can be different.