Documentation: add a guide for quarkus-info

[jmini]

I think the io.quarkus:quarkus-info deserves its own guide.

It is a small but very useful feature.

--> Announced here https://quarkus.io/blog/quarkus-3-0-0-cr1-released/#qinfo

But there is way more.

There is an extension page: https://quarkus.io/extensions/io.quarkus/quarkus-info/

A lot of spring users are wondering what is the replacement for the "actuator" feature. (I am not a Spring user myself, but I think there is at least some overlap with quarkus-info)

Example questions:

• https://stackoverflow.com/questions/73412518/how-can-i-show-the-build-and-application-version-in-quarkus-application
• https://stackoverflow.com/questions/74852176/it-is-any-possibility-to-use-actuators-info-or-gorylenko-git-propeties-in-quar

Configs

Related configs: quakurs.info.* configs (I think there is a way to display the table of related configs)

Features

Some interesting features that could be highlighted:

Info beans can be injected

Example:

	@Inject
	io.quarkus.info.GitInfo info;

    @GET
    @Produces(MediaType.TEXT_PLAIN)
    public String hello() {
        return "Hello from Quarkus REST: " + info.latestCommitId();
    }

--> See #32994

In case you need the commit-id or something else as part some features you already provide.

Or also a quarkus-based CLI app will not have a /q/info endpoint.

Apps/Extensions can contribute to /q/info

I didn't tried it but see:
--> #37994

---

Related issues:

• Provide Git information on runtime (Alternative to SpringBoot build-info) #29995
• Information endpoint #13598
• Dev UI: Info needs to know which git commit id selects #36027

[quarkus-bot]

/cc @MichalMaler (documentation), @rolfedh (documentation), @sheilamjones (documentation)

[jmini]

Pointers from @gsmet on Zullip:

I would start simple and create a guide similar to https://quarkus.io/guides/validation
the guides are there: https://.com/quarkusio/quarkus/tree/main/docs/src/main/asciidoc
the one above is validation.adoc

then to iterate on the doc, these aliases are useful: https://.com/quarkusio/quarkus/blob/main/CONTRIBUTING.md#using-aliases

you do one global build-docs at the root, then you just rebuild the docs module only

my advice: start small and then you can iterate on it