mirror of
https://github.com/ilyakooo0/nixpkgs.git
synced 2024-10-14 08:31:40 +03:00
64c94bd40a
This makes it possible for other systemd units to depend on keycloak.service using `after` and `wants` relationships, and systemd will actually wait for Keycloak to finish its initialization before starting any dependent units. This can be important for services like oauth2-proxy, which (when configured to use Keycloak as its auth provider) will fail to start until Keycloak's `.well-known/openid-configuration` endpoint is available.
26 lines
1.0 KiB
Nix
26 lines
1.0 KiB
Nix
{ callPackage, fetchMavenArtifact }:
|
|
|
|
{
|
|
scim-for-keycloak = callPackage ./scim-for-keycloak {};
|
|
scim-keycloak-user-storage-spi = callPackage ./scim-keycloak-user-storage-spi {};
|
|
keycloak-discord = callPackage ./keycloak-discord {};
|
|
keycloak-metrics-spi = callPackage ./keycloak-metrics-spi {};
|
|
keycloak-restrict-client-auth = callPackage ./keycloak-restrict-client-auth {};
|
|
|
|
# These could theoretically be used by something other than Keycloak, but
|
|
# there are no other quarkus apps in nixpkgs (as of 2023-08-21)
|
|
quarkus-systemd-notify = (fetchMavenArtifact {
|
|
groupId = "io.quarkiverse.systemd.notify";
|
|
artifactId = "quarkus-systemd-notify";
|
|
version = "1.0.1";
|
|
hash = "sha256-3I4j22jyIpokU4kdobkt6cDsALtxYFclA+DV+BqtmLY=";
|
|
}).passthru.jar;
|
|
|
|
quarkus-systemd-notify-deployment = (fetchMavenArtifact {
|
|
groupId = "io.quarkiverse.systemd.notify";
|
|
artifactId = "quarkus-systemd-notify-deployment";
|
|
version = "1.0.1";
|
|
hash = "sha256-xHxzBxriSd/OU8gEcDG00VRkJYPYJDfAfPh/FkQe+zg=";
|
|
}).passthru.jar;
|
|
}
|