feat(full): configure external QQQ profile (#5) #15

Merged
KofTwentyTwo merged 2 commits from feature/GH-5-full-profile into develop 2026-09-26 14:10:42 +00:00
KofTwentyTwo commented 2026-09-26 14:08:26 +00:00 (Migrated from github.com)

Closes #5.

The full profile selects PostgreSQL, MySQL, MongoDB, MinIO-backed S3, and SFTP tables; configures Artemis and RabbitMQ destinations, Mailpit SMTP, and Keycloak OIDC with role permissions from qbit-user-role-permissions. External binding requires an explicit QQQ_ALL_BIND_HOST. The shaded jar selects core or full through QQQ_ALL_PROFILE.

The OIDC customizer resolves role metadata during authentication under a scoped system session and restores the previous session afterward. A regression test covers the null-session login path.

Validation: mvn -o -pl qqq-all-app -am verify -q passed (12 unit tests and the packaged core jar integration test). Independent review passed. Live full-profile backend, broker, and OIDC checks follow with Compose in #7 and CI smoke in #8.

Closes #5. The `full` profile selects PostgreSQL, MySQL, MongoDB, MinIO-backed S3, and SFTP tables; configures Artemis and RabbitMQ destinations, Mailpit SMTP, and Keycloak OIDC with role permissions from `qbit-user-role-permissions`. External binding requires an explicit `QQQ_ALL_BIND_HOST`. The shaded jar selects `core` or `full` through `QQQ_ALL_PROFILE`. The OIDC customizer resolves role metadata during authentication under a scoped system session and restores the previous session afterward. A regression test covers the null-session login path. Validation: `mvn -o -pl qqq-all-app -am verify -q` passed (12 unit tests and the packaged core jar integration test). Independent review passed. Live full-profile backend, broker, and OIDC checks follow with Compose in #7 and CI smoke in #8.
Sign in to join this conversation.