This is an automated email from the ASF dual-hosted git repository.

davsclaus pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel.git


The following commit(s) were added to refs/heads/main by this push:
     new efa24a173c0 Camel-18170 - Updating the Google Calendar component doc 
(#7832)
efa24a173c0 is described below

commit efa24a173c09302d47f942c3ec3783b0b31cb8e9
Author: Rhuan Rocha <[email protected]>
AuthorDate: Tue Jun 21 02:02:13 2022 -0300

    Camel-18170 - Updating the Google Calendar component doc (#7832)
    
    Signed-off-by: Rhuan Rocha <[email protected]>
---
 docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_18.adoc | 5 +++++
 1 file changed, 5 insertions(+)

diff --git 
a/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_18.adoc 
b/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_18.adoc
index e6e431bb557..d01c841e46f 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_18.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_18.adoc
@@ -29,6 +29,11 @@ The `camel-milo` feature has been removed.
 The `keyResource` option has been changed to `serviceAccountKey` to match to 
Google semantic. Then, if you use the `keyResource` 
 to Google Drive component, you should update it to  `serviceAccountKey`.
 
+=== camel-google-calendar
+
+The `keyResource` option has been changed to `serviceAccountKey` to match to 
Google semantic. Then, if you use the `keyResource` 
+to Google Calendar component, you should update it to  `serviceAccountKey`.
+
 === camel-yaml-dsl
 
 The YAML DSL schema files `camel-yaml-dsl.json` and `camelYamlDsl.json` has 
been moved from root to `schema` sub folder in the JAR.

Reply via email to