anchor.diff:  
   The `quarkus-google-cloud-functions` extension scans your project for a class that directly implements the Google Cloud `HttpFunction`, `BackgroundFunction` or `RawBakgroundFunction` interface.
   It must find a class in your project that implements one of these interfaces or it will throw a build time failure.
  -If it finds more than one function class, a build time exception will also be thrown.
  +If it finds more than one function classes, a build time exception will also be thrown.
   
   Sometimes, though, you might have a few related functions that share code and creating multiple maven modules is just
   an overhead you don't want to do.  The extension allows you to bundle multiple functions in one
  
positive.code: curl localhost:8080 -d '{"data":{"greeting":"world"}}'
  ----
  
  This will call your PubSub background function with a PubSubMessage `{"greeting":"world"}`.
negative.code: The entry point must always be set to `io.quarkus.gcp.functions.QuarkusBackgroundFunction` as this is the class that integrates Cloud Functions with Quarkus.
  ====
  
  To trigger the event, you can send a file to the `hello_topic` topic of you can use gcloud to simulate one:
  
  [source]
  ----
  gcloud functions call quarkus-example-pubsub --data '{"data":{"greeting":"world"}}'
  ----
  
  == Testing locally
  
  The easiest way to locally test your function is using the Cloud Function invoker JAR.
  