This is an automated email from the ASF dual-hosted git repository.
nferraro pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel-k.git
commit 9fe31636911874aff86301d57128ee90dd238eda
Author: John Poth <poth.j...@gmail.com>
AuthorDate: Wed Dec 16 12:50:04 2020 +0100
Leverage Quarkus' Service Binding support #13617
---
proposals/service-binding/service-binding.adoc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/proposals/service-binding/service-binding.adoc
b/proposals/service-binding/service-binding.adoc
index 41941ac..809b110 100644
--- a/proposals/service-binding/service-binding.adoc
+++ b/proposals/service-binding/service-binding.adoc
@@ -94,7 +94,7 @@ The proposed architecture is illustrated in the diagram below:
image::assets/service-binding.svg[Camel K Integration Service Binding]
-where the `Secret` created by the _Service Binding Operator_ holds the binding
information. The `Integration` could then reference these properties just like
any other `Secret` properties. A special mapping may be created by Camel-k to
avoid the user having to reference the `Secret` name in their configuration e.g
just `{DB_PORT}` instead of `{secret:secret-name/DB_PORT}`.
+where the `Secret` created by the _Service Binding Operator_ holds the binding
information. Quarkus' Service Binding
https://github.com/quarkusio/quarkus/issues/13617[support] could then be
leveraged to configure the `Integration`.
The steps `2-4` would not happen if the `ServiceBinding` is created beforehand.
