-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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.
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
Quarkus-info extension could provide beans available to applications #32994
Comments
/cc @geoand |
So if I understand correctly you just want access to the data via CDI which you would then use to build your own endpoint? |
Yes. In my particular case the endpoint + a startup log are using the data from
where gitConfig is a ConfigMapping created from the properties file create by |
Gotcha. I think this makes sense |
Not sure what is the easiest, but could also be as simple as having is statically available as ProcessorInfo does. |
Allow to inject info extension data as beans
I was trying to use this capability (Quarkus version 3.0.0) with the following behavior:
Any ideas?
|
I've never seen that. Do you have a sample application thta exhibits that behavior? |
I use GitInfo from the dependency Quarkus-info:
|
I tried it and it worked just fine for me. |
Description
In our applicaiton we use
git-commit-id-maven-plugin
to create a git.properties, which we add to the build viaquarkus.config.locations
I think it would be good if we could remove that and use quarkus-info and inject or a composite bean or multiple bean for; JavaInfo, GitInfo, BuildInfo, OsInfo, which could then be use through an application. This way we could easily customize also the format we want and/or need via a custom endpoint, or not use an endpoint at all but have it available for logging or any other purposes.
Implementation ideas
No response
The text was updated successfully, but these errors were encountered: