feat(pivot,ci): per-database pivot apps with container builds - #58
Merged
stbischof merged 1 commit intoAug 17, 2026
Merged
Conversation
pivot becomes one app per database, each with its own runbundle list. A common module carries the shared server configuration and env mapping; the database modules contribute only their datasource, dialect and driver bundles. Every app also carries the split connector rowset bundles and the role resolution bundle - without the former no MDSCHEMA request is answered, without the latter the XMLA servlet never activates. The DuckDB app marks its pool connections with the read-only mode of the DataSource, since the driver refuses to re-mark a connection. The images offer HTTP Basic authentication against LDAP (auth.basic + auth.store.ldap, DAANSE_LDAP_* variables, roles from LDAP groups); anonymous requests stay accepted until DAANSE_AUTH_ANONYMOUS=false. Each app gets a Dockerfile (OCI-labelled) and a Testcontainers integration test that builds the image from the real Dockerfile (or verifies a pre-built one via -Dpivot.image). CI builds every image, verifies it with the integration test and pushes it multi-arch; build_images.sh does the same locally. The per database READMEs plus the shared README.container.md form the Docker Hub description the CI publishes. Self contained demos live in common/example: a Compose demo, the same as a Kubernetes pod for Podman/kubectl, and a Compose demo with an LLDAP side container that is exercised end-to-end by LdapAuthPivotIT. The playground gets its own h2 dependencies: it required h2 through the application parent, which now ships duckdb for the probe instead - the bndrun resolve failed on CI while the export, which only checks the pinned runbundles, still passed. Signed-off-by: Stefan Bischof <stbischof@bipolis.org>
stbischof
force-pushed
the
feat/rowset-packages-split
branch
from
August 17, 2026 06:23
427191e to
420436e
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
pivot becomes one app per database, each with its own runbundle list. A common module carries the shared server configuration and env mapping; the database modules contribute only their datasource, dialect and driver bundles. Every app also carries the split connector rowset bundles and the role resolution bundle - without the former no MDSCHEMA request is answered, without the latter the XMLA servlet never activates. The DuckDB app marks its pool connections with the read-only mode of the DataSource, since the driver refuses to re-mark a connection.
The images offer HTTP Basic authentication against LDAP (auth.basic + auth.store.ldap, DAANSE_LDAP_* variables, roles from LDAP groups); anonymous requests stay accepted until DAANSE_AUTH_ANONYMOUS=false.
Each app gets a Dockerfile (OCI-labelled) and a Testcontainers integration test that builds the image from the real Dockerfile (or verifies a pre-built one via -Dpivot.image). CI builds every image, verifies it with the integration test and pushes it multi-arch; build_images.sh does the same locally. The per database READMEs plus the shared README.container.md form the Docker Hub description the CI publishes. Self contained demos live in common/example: a Compose demo, the same as a Kubernetes pod for Podman/kubectl, and a Compose demo with an LLDAP side container that is exercised end-to-end by LdapAuthPivotIT.