From 8a88f0cf54d0c5a182bdb062de085e74e9b4b344 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?J=C3=A9r=C3=A9mie=20Bresson?= Date: Mon, 4 Nov 2024 15:20:38 +0100 Subject: [PATCH] Update smallrye-graphql-client.adoc --- docs/src/main/asciidoc/smallrye-graphql-client.adoc | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/src/main/asciidoc/smallrye-graphql-client.adoc b/docs/src/main/asciidoc/smallrye-graphql-client.adoc index c9928ffdec09e..fab9e282f1795 100644 --- a/docs/src/main/asciidoc/smallrye-graphql-client.adoc +++ b/docs/src/main/asciidoc/smallrye-graphql-client.adoc @@ -230,6 +230,12 @@ that the target of the client is the application that is being tested (typically This is useful if your application contains a GraphQL server-side API as well as a GraphQL client that is used for testing the API. +If you need to add an authorization header, or any other custom HTTP header (in our case +it's not required), this can be done with a configuration in the configuration file as well: +---- +quarkus.smallrye-graphql-client.star-wars-typesafe.header.HEADER-KEY=HEADER-VALUE +---- + `star-wars-typesafe` is the name of the configured client instance, and corresponds to the `configKey` in the `@GraphQLClientApi` annotation. If you don't want to specify a custom name, you can leave out the `configKey`, and then refer to it by using the fully qualified name of the interface.