have quarkus use user-agent when interacting with systems

[maxandersen]

Description

In #21458 user-agent used when calling amazon lambda apis is set to:

 USER_AGENT_VALUE = String.format(
            "quarkus/%s-%s",
            System.getProperty("java.vendor.version"),
            AbstractLambdaPollLoop.class.getPackage().getImplementationVersion());

and used in http url connection requests allowing Amazon to identify Quarkus usage.

We should do similar for other integrations that allow setting user agent.

Suggestion is to make a config property that defaults to something similar to above but include java.vendor and follow more defacto standard user-agent format.

Something like: "quarkus/2.13.0.Final java/19 (Eclipse Adoptium Temurin-19+36-202208180334)"

Using format: "quarkus/${quarkus.version} java/${java.vm.specification.version} (${java.vendor} ${java.vendor.version})"

Implementation ideas

No response

[geoand]

We should do similar for other integrations that allow setting user agent.

Do you have any such integrations in mind?

[maxandersen]

Do you have any such integrations in mind?

any use of http based apis, i.e. amazon, google, azure, kubernetes/openshift, would be my first thought.

[quarkus-bot]

/cc @Sanne, @aloubyansky, @geoand, @gsmet, @loicmathieu, @matejvasek, @patriot1burke, @radcortez, @stuartwdouglas

[mfpc]

Could anyone confirm if is this correct? Should I change another files? Please let me know
#30934

[geoand]

That's certainly part of what the issue is about :)

…

On Mon, Feb 6, 2023 at 8:00 PM Marcell Cruz ***@***.***> wrote: Could anyone confirm if this its correct? Should I change another files? Please let me know #30934 <#30934> — Reply to this email directly, view it on GitHub <#27889 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABBMDPZZR7LNYP7XLW3ZIFTWWE32BANCNFSM6AAAAAAQLFGIAE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[sberyozkin]

Exposing the fact Quarkus is used should be optional, it is exactly the same type of issue where someone does not want Server: Undertow or similar be reported in responses, we might've had related issues. Otherwise the information leak issues will just follow