You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/src/main/asciidoc/funqy-gcp-functions.adoc
+1-9Lines changed: 1 addition & 9 deletions
Original file line number
Diff line number
Diff line change
@@ -81,8 +81,6 @@ In this example, we will create two background functions and a cloud events func
81
81
Background functions allow you to react to Google Cloud events like PubSub messages, Cloud Storage events, Firestore events, ...
82
82
Cloud events functions allow you to react to supported events using the Cloud Events specification.
83
83
84
-
NOTE: Quarkus supports Cloud Functions gen 1 and gen 2. For an overview of Cloud Functions gen 2 see https://cloud.google.com/functions/docs/2nd-gen/overview[this page] on the Google Cloud Functions documentation. To use gen 2 you must add the `--gen2` parameter.
85
-
86
84
[source,java]
87
85
----
88
86
import jakarta.inject.Inject;
@@ -231,8 +229,6 @@ You can also simply add a file to Cloud Storage using the command line of the we
231
229
232
230
=== Cloud Events Functions - Cloud Storage
233
231
234
-
WARNING: Cloud Events Function is a feature of Cloud Functions gen 2 only.
235
-
236
232
Before deploying your function, you need to create a bucket.
237
233
238
234
[source,bash]
@@ -244,7 +240,7 @@ Then, use this command to deploy to Google Cloud Functions:
Copy file name to clipboardExpand all lines: docs/src/main/asciidoc/gcp-functions-http.adoc
+1-3Lines changed: 1 addition & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -63,13 +63,11 @@ one for Reactive routes and one for xref:funqy-http.adoc[Funqy HTTP].
63
63
[NOTE]
64
64
====
65
65
These various endpoints are for demonstration purposes.
66
-
For real life applications, you should choose one of this technology and stick to it.
66
+
For real life applications, you should choose one of these technologies and stick to it.
67
67
====
68
68
69
69
If you don't need endpoints of each type, you can remove the corresponding extensions from your `pom.xml`.
70
70
71
-
NOTE: Quarkus supports Cloud Functions gen 1 and gen 2. For an overview of Cloud Functions gen 2 see https://cloud.google.com/functions/docs/2nd-gen/overview[this page] on the Google Cloud Functions documentation. To use gen 2 you must and add the `--gen2` parameter.
Copy file name to clipboardExpand all lines: docs/src/main/asciidoc/gcp-functions.adoc
+1-11Lines changed: 1 addition & 11 deletions
Original file line number
Diff line number
Diff line change
@@ -58,8 +58,6 @@ gcloud auth login
58
58
For this example project, we will create four functions, one `HttpFunction`, one `BackgroundFunction` (Storage event),
59
59
one `RawBackgroundFunction` (PubSub event) and one `CloudEventsFunction` (storage event using the Cloud Events specification).
60
60
61
-
NOTE: Quarkus supports Cloud Functions gen 1 and gen 2. For an overview of Cloud Functions gen 2 see https://cloud.google.com/functions/docs/2nd-gen/overview[this page] on the Google Cloud Functions documentation. To use gen 2 you must add the `--gen2` parameter.
62
-
63
61
== Choose Your Function
64
62
65
63
The `quarkus-google-cloud-functions` extension scans your project for a class that directly implements the Google Cloud `HttpFunction`, `BackgroundFunction`, `RawBackgroundFunction` or `CloudEventsFunction` interface.
@@ -193,8 +191,6 @@ public class RawBackgroundFunctionPubSubTest implements RawBackgroundFunction {
193
191
194
192
=== The CloudEventsFunction
195
193
196
-
WARNING: `CloudEventsFunction` is a feature of Cloud Functions gen 2 only.
197
-
198
194
This `CloudEventsFunction` is triggered by a Cloud Events Storage event, you can use any Cloud Events supported by Google Cloud instead.
0 commit comments