This is an automated email from the ASF dual-hosted git repository. github-bot pushed a change to branch regen_bot in repository https://gitbox.apache.org/repos/asf/camel.git.
omit 2c421e0 Regen for commit c87af09f979387dd8d04c3664fb1b8bdb1a40c41 add 8444e2d Regen for commit c87af09f979387dd8d04c3664fb1b8bdb1a40c41 add 52b53bd CAMEL-16273 - Camel-google-* cloud components: Make the serviceAccountKey explicitly configurable - Camel-google-pubsub, mark service account key as required add bcd1fe8 CAMEL-16273 - Camel-google-* cloud components: Make the serviceAccountKey explicitly configurable - Camel-google-pubsub - Regen This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (2c421e0) \ N -- N -- N refs/heads/regen_bot (bcd1fe8) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. No new revisions were added by this update. Summary of changes: .../resources/org/apache/camel/catalog/components/google-pubsub.json | 2 +- .../org/apache/camel/catalog/docs/google-pubsub-component.adoc | 2 +- .../org/apache/camel/component/google/pubsub/google-pubsub.json | 2 +- .../camel-google-pubsub/src/main/docs/google-pubsub-component.adoc | 2 +- .../org/apache/camel/component/google/pubsub/GooglePubsubEndpoint.java | 1 + .../camel/builder/endpoint/dsl/GooglePubsubEndpointBuilderFactory.java | 3 +++ docs/components/modules/ROOT/pages/google-pubsub-component.adoc | 2 +- 7 files changed, 9 insertions(+), 5 deletions(-)