Skip to content

docs: Clarify on the current state of druid opa authorizer #1545

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
sbernauer wants to merge 1 commit into
base: main
Choose a base branch
from
+14 −0
Open

docs: Clarify on the current state of druid opa authorizer #1545

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions druid/boil-config.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,4 +31,18 @@ java-devel = "21"
[versions."37.0.0".build-arguments]
# We don't need to bump this if no code changed in https://github.com/stackabletech/druid-opa-authorizer
# But a PR still needs to be raised to add/remove versions and ensure it still builds.

# IMHO this is a mess. We fetch the release from https://repo.stackable.tech/repository/packages/druid/druid-opa-authorizer-${AUTHORIZER_VERSION}.tar.gz
# and use that. There hasn't been a release since 2025-06-02. It's a random .tar.gz of a .jar file in Nexus.
# It was compiled against
#
# * A totally different Druid version
# * Different jackson version
# * Different guava version
# * Different guice version
# * Different Java version (this should be fine)
#
# Yes, this seems to have worked in the past, but we should build the authorizer from source (as we
# do with others). It should also require a mandatory profile (no activation by default), so that
# the build fails on an unsupported Druid version.
authorizer-version = "0.7.0"