feat: read from postgres and fix the container main class - #150
Closed
TheMeinerLP wants to merge 2 commits into
Closed
feat: read from postgres and fix the container main class#150TheMeinerLP wants to merge 2 commits into
TheMeinerLP wants to merge 2 commits into
Conversation
Two things stand between this service and running in the cluster. It talks to MariaDB. The Vulpes data moved to the shared CNPG Postgres with the backend, and no MariaDB `vulpes` database exists any more -- so pointed at the cluster it would find nothing to read. The Postgres driver was not even on the classpath, and driver and dialect were hardcoded, so no amount of configuration could have fixed it from the outside. Both are now settable (DB_DRIVER, DB_DIALECT) with the MariaDB values kept as defaults, leaving the docker-compose setup beside this repo working exactly as before; the deployment overrides url, driver, dialect and credentials together. And charts/vulpes-generator probes /health and points a ServiceMonitor at /prometheus -- endpoints application.yml has configured all along, but which nothing served, because micronaut-management was missing from the dependencies. The probes would have 404'd and the pod would never have turned ready. micrometer is added alongside it so /prometheus has something to report. compileJava passes.
The package rename from net.theevilreaper.* to net.onelitefeather.* never reached application.mainClass, so Micronaut wrote a stale Main-Class into application.jar. The container entrypoint runs `java -jar /home/app/application.jar`, which made every pod die with ClassNotFoundException: net.theevilreaper.vulpes.generator.VulpesGenerator. Verified via `./gradlew buildLayers`: the manifest now reads Main-Class: net.onelitefeather.vulpes.generator.VulpesGenerator.
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.
Was drin ist
feat: read from postgres and answer the chart's probesfix: point mainClass at the renamed packagenet.theevilreaper.*→net.onelitefeather.*hatteapplication.mainClassinbuild.gradle.ktsnie erreicht.Main-Classinapplication.jar; der generierte Entrypoint istjava -jar /home/app/application.jar.Could not find or load main class net.theevilreaper.vulpes.generator.VulpesGenerator.Verifikation
./gradlew buildLayersneu gebaut und das Manifest geprüft:Main-Class: net.onelitefeather.vulpes.generator.VulpesGeneratornet/onelitefeather/vulpes/generator/VulpesGenerator.classliegt im JarEs war die letzte aktive
theevilreaper-Referenz im Repo (die verbleibende insettings.gradle.kts:50ist auskommentiert).Offener Punkt (nicht Teil dieses PRs)
src/main/resources/gradle_template.zipist lokal untracked. Die Datei landet imresources-Layer des Images, würde im CI-Build aber fehlen.