Merge branch 'develop' into 'main'

# OOP Data Lab — deployment configuration.

#

# Copy to .env and fill in. Never commit .env.

# Values marked PLACEHOLDER depend on open question F1 in the architecture

# spec (ingress hostname) and are expected to change once

# the deployment target is fixed.

# Compose profile gating (implementation-and-delivery §Q.3). Keeps `docker compose up`

# working without repeating `--profile data-lab` on every command.

COMPOSE_PROFILES=data-lab

# ---------------------------------------------------------------------------

# Public identity of this deployment (F1)

# ---------------------------------------------------------------------------

# Public base URI used to mint dataset/distribution/catalogue URIs. It MUST be

# stable for the life of the catalogue — minted URIs are persistent identifiers

# (MAP §12) and changing this orphans every record already published.

DATA_LAB_BASE_URI=https://oop.example.org/data-lab/

# Browser origin allowed to call the hub (CORS). Single origin, never "*".

DATA_LAB_PUBLIC_ORIGIN=https://oop.example.org

# ---------------------------------------------------------------------------

# Catalogues (REQ-DL-07) — one deployment, two catalogues

# ---------------------------------------------------------------------------

CATALOGUE_ID=oop-org

CATALOGUE_STAGING_ID=oop-org-staging

CATALOGUE_TITLE="OOP Data Lab"

CATALOGUE_PUBLISHER=OOP

# ---------------------------------------------------------------------------

# Secrets — generate per deployment, inject from the platform secret store

# ---------------------------------------------------------------------------

# piveau API keys. Only the Data Lab API and operator tooling use the hub key;

# machine clients use tokens of their own Keycloak client (REQ-DL-11). Generate with:

#   openssl rand -hex 32

PIVEAU_REPO_API_KEY=PLACEHOLDER-generate-me

PIVEAU_SEARCH_API_KEY=PLACEHOLDER-generate-me

# Virtuoso administrative password (both instances). Keep it to 16 characters or

# fewer: Virtuoso 7.2.14 refuses to log in with a longer one ("Bad login"), which

# surfaces as 401 on every catalogue write. Generate with:  openssl rand -hex 8

VIRTUOSO_DBA_PASSWORD=PLACEHOLDER-generate-me

# ---------------------------------------------------------------------------

# Identity — platform Keycloak, realm `dataspace`

# Keycloak must be 26.4 or newer: piveau access control creates Keycloak groups

# with a `description`, which older servers reject (400) - nothing is then

# authorised. Tested with 26.4.

# ---------------------------------------------------------------------------

KEYCLOAK_SERVER_URL=https://oop.example.org/auth

KEYCLOAK_REALM=dataspace

KEYCLOAK_ISSUER=https://oop.example.org/auth/realms/dataspace

# Scheme + host of Keycloak, no path. Used in the admin UI's Content-Security-Policy.

KEYCLOAK_ORIGIN=https://oop.example.org

# Confidential client of piveau access control: the resource server that holds

# one Keycloak resource per catalogue. piveau-hub-repo and -search validate tokens

# with it, hub-repo creates the catalogue groups and resources through it, and

# the Data Lab API asks it what a caller may do.

KEYCLOAK_HUB_CLIENT_ID=piveau-hub-repo

KEYCLOAK_HUB_CLIENT_SECRET=PLACEHOLDER-from-keycloak

# Public client for the Data Lab UI (Authorization Code + PKCE).

KEYCLOAK_ADMIN_UI_CLIENT_ID=data-lab-admin

# Confidential service-account client the Data Lab API uses to look up users and

# to put them into / take them out of a catalogue's role groups (needs

# realm-management roles, see docs/deployment.md).

KEYCLOAK_API_CLIENT_ID=data-lab-api

KEYCLOAK_API_CLIENT_SECRET=PLACEHOLDER-from-keycloak

# ---------------------------------------------------------------------------

# Images (implementation-and-delivery §Q.1 — pinned, never :latest)

# ---------------------------------------------------------------------------

# Access control v2 needs hub-repo >= 3.4 (3.3.11 predates the access-level property); 4.x is published on

# Docker Hub as piveau/hub-repo, hub-search stays on the GitLab registry. Tested pair: 4.4.3 + 5.3.11.

PIVEAU_HUB_REPO_IMAGE=piveau/hub-repo:4.4.3

# 5.1.25 does not start against Elasticsearch 7.17; hub-search 5.x runs on ES 8.13.4.

PIVEAU_HUB_SEARCH_IMAGE=registry.gitlab.com/piveau/hub/piveau-hub-search:5.3.11

# The two images built from this repo. CI publishes them to the project's container registry (GitLab: Deploy >

# Container Registry), tagged per branch: `<branch>` moves with every build, `ci-<branch>-<sha>` never changes.

# A deployment pins one, for example:

#   DATA_LAB_API_IMAGE=<registry>/oop/code/data-lab/data-lab-api:ci-main-1b4713e

#   DATA_LAB_UI_IMAGE=<registry>/oop/code/data-lab/data-lab-admin-ui:ci-main-1b4713e

# With the dev overlay (local work) compose builds them from source and gives them these names, so the defaults

# below work as they are.

DATA_LAB_API_IMAGE=oop-data-lab-api:local

DATA_LAB_UI_IMAGE=oop-data-lab-admin-ui:local

# Both Virtuoso instances run the same image. The 6G-DALI baseline had the

# shadow store on 7.2.8 (and on Ubuntu rather than Alpine) — drift, not a

# requirement: both speak the same SPARQL Graph Store protocol. Staying on

# 7.2.14 rather than the current 7.2.17 keeps assumption E3 intact, since

# that is the version proven against piveau-hub-repo (tested again with 4.4.3).

VIRTUOSO_IMAGE=openlink/virtuoso-opensource-7:7.2.14-alpine

ELASTICSEARCH_IMAGE=docker.elastic.co/elasticsearch/elasticsearch:8.13.4

# ---------------------------------------------------------------------------

# Runtime tuning

# ---------------------------------------------------------------------------

# INFO in any deployed environment — TRACE leaks record contents to stdout.

PIVEAU_LOG_LEVEL=INFO

HUB_JAVA_OPTS="-Xms1g -Xmx2g"

SEARCH_JAVA_OPTS="-Xms1g -Xmx2g"

ES_JAVA_OPTS="-Xms2g -Xmx4g"

# Shell scripts run inside Linux containers and on operators' hosts: a CRLF checkout on Windows breaks them

# ("/bin/sh^M: bad interpreter"). Keep them LF whatever core.autocrlf says.

*.sh text eol=lf

docker-entrypoint.d/* text eol=lf

*.conf text eol=lf

*.template text eol=lf

Dockerfile text eol=lf

local/*.py text eol=lf

Makefile text eol=lf

.gitlab-ci.yml text eol=lf

# Local configuration — never commit resolved secrets

.env

.env.*

!.env.example

# Runtime state

data/

*.log

# Editors / OS

.idea/

.vscode/

.DS_Store

Thumbs.db

# Python caches and virtualenvs (api/)

__pycache__/

*.pyc

.pytest_cache/

.venv/

venv/

# Node (admin-ui/ also ignores these itself)

node_modules/

dist/

# Generated by local/local-up.sh (realm copy, env file) - local trial only

local/.generated/

# Data Lab CI: test the two OOP-built components, check the deployment files, and publish their images.

#

# Only data-lab-api and data-lab-admin-ui are built here; piveau, Virtuoso, Elasticsearch and Keycloak are pinned

# upstream images (see .env.example). Images go to this project's GitLab Container Registry, tagged per branch like

# the Open Exposure Gateway's:

#

#   $CI_REGISTRY_IMAGE/data-lab-api:ci-<branch>-<short-sha>       immutable: one per commit

#   $CI_REGISTRY_IMAGE/data-lab-api:<branch>                      moves: the latest build of that branch

#   $CI_REGISTRY_IMAGE/data-lab-admin-ui:...                      same two tags

#

# main and develop build automatically; any other branch (for example feat/datalab) builds when the

# build-and-push job is started by hand from the pipeline page.

stages:

  - test

  - build-and-push

api-test:

  stage: test

  image: python:3.12-slim

  script:

    - cd api

    - pip install --no-cache-dir -r requirements-dev.txt

    - pytest -q

ui-test:

  stage: test

  image: node:22-alpine

  script:

    - cd admin-ui

    - npm ci

    - npx tsc --noEmit

    - npx vitest run

    - npm run build

# The compose files must stay valid for every combination people use, and the scripts must at least parse.

deployment-files:

  stage: test

  image: docker:cli

  before_script:

    - apk add --no-cache bash

  script:

    - docker compose -f compose/docker-compose.yml --env-file .env.example config --quiet

    - docker compose -f compose/docker-compose.yml -f compose/docker-compose.dev.yml --env-file .env.example config --quiet

    - >

      docker compose -f compose/docker-compose.yml -f compose/docker-compose.dev.yml -f compose/docker-compose.local.yml

      --env-file .env.example config --quiet

    - for f in bootstrap/bootstrap.sh scripts/*.sh local/*.sh admin-ui/docker-entrypoint.d/*.sh; do bash -n "$f" || exit 1; done

build-and-push:

  stage: build-and-push

  image: docker:cli

  parallel:

    matrix:

      - COMPONENT: data-lab-api

        CONTEXT: api

      - COMPONENT: data-lab-admin-ui

        CONTEXT: admin-ui

  variables:

    DOCKER_HOST: tcp://docker:2375

    DOCKER_TLS_CERTDIR: ""

  services:

    - docker:dind

  before_script:

    - docker info

  script:

    - export IMAGE="$CI_REGISTRY_IMAGE/$COMPONENT"

    - export COMMIT_TAG="ci-${CI_COMMIT_REF_SLUG}-${CI_COMMIT_SHORT_SHA}"

    - echo "$CI_REGISTRY_PASSWORD" | docker login -u "$CI_REGISTRY_USER" "$CI_REGISTRY" --password-stdin

    - docker buildx build --provenance=false --network=host -t "$IMAGE:$COMMIT_TAG" -t "$IMAGE:$CI_COMMIT_REF_SLUG" --push "$CONTEXT"

    - docker logout "$CI_REGISTRY"

    - echo "published $IMAGE:$COMMIT_TAG and $IMAGE:$CI_COMMIT_REF_SLUG"

  rules:

    - if: '$CI_COMMIT_BRANCH == "main" || $CI_COMMIT_BRANCH == "develop"'

    - if: '$CI_COMMIT_BRANCH'

      when: manual

      allow_failure: true

                                 Apache License

                           Version 2.0, January 2004

                        http://www.apache.org/licenses/

   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

   1. Definitions.

      "License" shall mean the terms and conditions for use, reproduction,

      and distribution as defined by Sections 1 through 9 of this document.

      "Licensor" shall mean the copyright owner or entity authorized by

      the copyright owner that is granting the License.

      "Legal Entity" shall mean the union of the acting entity and all

      other entities that control, are controlled by, or are under common

      control with that entity. For the purposes of this definition,

      "control" means (i) the power, direct or indirect, to cause the

      direction or management of such entity, whether by contract or

      otherwise, or (ii) ownership of fifty percent (50%) or more of the

      outstanding shares, or (iii) beneficial ownership of such entity.

      "You" (or "Your") shall mean an individual or Legal Entity

      exercising permissions granted by this License.

      "Source" form shall mean the preferred form for making modifications,

      including but not limited to software source code, documentation

      source, and configuration files.

      "Object" form shall mean any form resulting from mechanical

      transformation or translation of a Source form, including but

      not limited to compiled object code, generated documentation,

      and conversions to other media types.

      "Work" shall mean the work of authorship, whether in Source or

      Object form, made available under the License, as indicated by a

      copyright notice that is included in or attached to the work

      (an example is provided in the Appendix below).

      "Derivative Works" shall mean any work, whether in Source or Object

      form, that is based on (or derived from) the Work and for which the

      editorial revisions, annotations, elaborations, or other modifications

      represent, as a whole, an original work of authorship. For the purposes

      of this License, Derivative Works shall not include works that remain

      separable from, or merely link (or bind by name) to the interfaces of,

      the Work and Derivative Works thereof.

      "Contribution" shall mean any work of authorship, including

      the original version of the Work and any modifications or additions

      to that Work or Derivative Works thereof, that is intentionally

      submitted to Licensor for inclusion in the Work by the copyright owner

      or by an individual or Legal Entity authorized to submit on behalf of

      the copyright owner. For the purposes of this definition, "submitted"

      means any form of electronic, verbal, or written communication sent

      to the Licensor or its representatives, including but not limited to

      communication on electronic mailing lists, source code control systems,

      and issue tracking systems that are managed by, or on behalf of, the

      Licensor for the purpose of discussing and improving the Work, but

      excluding communication that is conspicuously marked or otherwise

      designated in writing by the copyright owner as "Not a Contribution."

      "Contributor" shall mean Licensor and any individual or Legal Entity

      on behalf of whom a Contribution has been received by Licensor and

      subsequently incorporated within the Work.

   2. Grant of Copyright License. Subject to the terms and conditions of

      this License, each Contributor hereby grants to You a perpetual,

      worldwide, non-exclusive, no-charge, royalty-free, irrevocable

      copyright license to reproduce, prepare Derivative Works of,

      publicly display, publicly perform, sublicense, and distribute the

      Work and such Derivative Works in Source or Object form.

   3. Grant of Patent License. Subject to the terms and conditions of

      this License, each Contributor hereby grants to You a perpetual,

      worldwide, non-exclusive, no-charge, royalty-free, irrevocable

      (except as stated in this section) patent license to make, have made,

      use, offer to sell, sell, import, and otherwise transfer the Work,

      where such license applies only to those patent claims licensable

      by such Contributor that are necessarily infringed by their

      Contribution(s) alone or by combination of their Contribution(s)

      with the Work to which such Contribution(s) was submitted. If You

      institute patent litigation against any entity (including a

      cross-claim or counterclaim in a lawsuit) alleging that the Work

      or a Contribution incorporated within the Work constitutes direct

      or contributory patent infringement, then any patent licenses

      granted to You under this License for that Work shall terminate

      as of the date such litigation is filed.

   4. Redistribution. You may reproduce and distribute copies of the

      Work or Derivative Works thereof in any medium, with or without

      modifications, and in Source or Object form, provided that You

      meet the following conditions:

      (a) You must give any other recipients of the Work or

          Derivative Works a copy of this License; and

      (b) You must cause any modified files to carry prominent notices

          stating that You changed the files; and

      (c) You must retain, in the Source form of any Derivative Works

          that You distribute, all copyright, patent, trademark, and

          attribution notices from the Source form of the Work,

          excluding those notices that do not pertain to any part of

          the Derivative Works; and

      (d) If the Work includes a "NOTICE" text file as part of its

          distribution, then any Derivative Works that You distribute must

          include a readable copy of the attribution notices contained

          within such NOTICE file, excluding those notices that do not

          pertain to any part of the Derivative Works, in at least one

          of the following places: within a NOTICE text file distributed

          as part of the Derivative Works; within the Source form or

          documentation, if provided along with the Derivative Works; or,

          within a display generated by the Derivative Works, if and

          wherever such third-party notices normally appear. The contents

          of the NOTICE file are for informational purposes only and

          do not modify the License. You may add Your own attribution

          notices within Derivative Works that You distribute, alongside

          or as an addendum to the NOTICE text from the Work, provided

          that such additional attribution notices cannot be construed

          as modifying the License.

      You may add Your own copyright statement to Your modifications and

      may provide additional or different license terms and conditions

      for use, reproduction, or distribution of Your modifications, or

      for any such Derivative Works as a whole, provided Your use,

      reproduction, and distribution of the Work otherwise complies with

      the conditions stated in this License.

   5. Submission of Contributions. Unless You explicitly state otherwise,

      any Contribution intentionally submitted for inclusion in the Work

      by You to the Licensor shall be under the terms and conditions of

      this License, without any additional terms or conditions.

      Notwithstanding the above, nothing herein shall supersede or modify

      the terms of any separate license agreement you may have executed

      with Licensor regarding such Contributions.

   6. Trademarks. This License does not grant permission to use the trade

      names, trademarks, service marks, or product names of the Licensor,

      except as required for reasonable and customary use in describing the

      origin of the Work and reproducing the content of the NOTICE file.

   7. Disclaimer of Warranty. Unless required by applicable law or

      agreed to in writing, Licensor provides the Work (and each

      Contributor provides its Contributions) on an "AS IS" BASIS,

      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or

      implied, including, without limitation, any warranties or conditions

      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A

      PARTICULAR PURPOSE. You are solely responsible for determining the

      appropriateness of using or redistributing the Work and assume any

      risks associated with Your exercise of permissions under this License.

   8. Limitation of Liability. In no event and under no legal theory,

      whether in tort (including negligence), contract, or otherwise,

      unless required by applicable law (such as deliberate and grossly

      negligent acts) or agreed to in writing, shall any Contributor be

      liable to You for damages, including any direct, indirect, special,

      incidental, or consequential damages of any character arising as a

      result of this License or out of the use or inability to use the

      Work (including but not limited to damages for loss of goodwill,

      work stoppage, computer failure or malfunction, or any and all

      other commercial damages or losses), even if such Contributor

      has been advised of the possibility of such damages.

   9. Accepting Warranty or Additional Liability. While redistributing

      the Work or Derivative Works thereof, You may choose to offer,

      and charge a fee for, acceptance of support, warranty, indemnity,

      or other liability obligations and/or rights consistent with this

      License. However, in accepting such obligations, You may act only

      on Your own behalf and on Your sole responsibility, not on behalf

      of any other Contributor, and only if You agree to indemnify,

      defend, and hold each Contributor harmless for any liability

      incurred by, or claims asserted against, such Contributor by reason

      of your accepting any such warranty or additional liability.

   END OF TERMS AND CONDITIONS

   APPENDIX: How to apply the Apache License to your work.

      To apply the Apache License to your work, attach the following

      boilerplate notice, with the fields enclosed by brackets "[]"

      replaced with your own identifying information. (Don't include

      the brackets!)  The text should be enclosed in the appropriate

      comment syntax for the file format. We also recommend that a

      file or class name and description of purpose be included on the

      same "printed page" as the copyright notice for easier

      identification within third-party archives.

   Copyright [yyyy] [name of copyright owner]

   Licensed under the Apache License, Version 2.0 (the "License");

   you may not use this file except in compliance with the License.

   You may obtain a copy of the License at

       http://www.apache.org/licenses/LICENSE-2.0

   Unless required by applicable law or agreed to in writing, software

   distributed under the License is distributed on an "AS IS" BASIS,

   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.

   See the License for the specific language governing permissions and

   limitations under the License.