Skip to content

chore: check in healthcheck that dataset exists (INFRA-872)#30

Merged
SamuelBoerlin merged 2 commits intomainfrom
feature/infra-872-check-for-dsp-repo-dataset-in-container-healthcheck
Sep 10, 2025
Merged

chore: check in healthcheck that dataset exists (INFRA-872)#30
SamuelBoerlin merged 2 commits intomainfrom
feature/infra-872-check-for-dsp-repo-dataset-in-container-healthcheck

Conversation

@SamuelBoerlin
Copy link
Contributor

@SamuelBoerlin SamuelBoerlin commented Sep 10, 2025

Now that we include and create the dsp-repo dataset on start we can check that it actually exists in the healthcheck.
This will also ensure that the container is only considered fully started/running once the dataset has been created.
/$/datasets requires authentication, so to keep that I added a healthcheck user with a randomly generated password with read-only (GET only) perms for that endpoint.
There would be org.apache.jena.fuseki.authz.LocalhostFilter to restrict access only to localhost, but unfortunately Shiro doesn't allow defining multiple chains per endpoint and so this restriction would also apply for the admin user, which won't work.

@linear
Copy link

linear bot commented Sep 10, 2025

Copy link
Contributor

@LukasStoeckli LukasStoeckli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@SamuelBoerlin SamuelBoerlin merged commit 0f3da70 into main Sep 10, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants