Open tomuben opened 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.
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:
-> 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
version
, which then will be copied to/build_info
build
andrelease
.