anchor.diff:  | Name | Description | Default | Type
   | *endpoint* (producer) | FunctionGraph url. Carries higher precedence than region parameter based client initialization |  | String
   | *functionName* (producer) | Name of the function to invoke |  | String
  -| *functionPackage* (producer) | Functions that can be logically grouped together |  | String
  +| *functionPackage* (producer) | Functions that can be logically grouped together | default | String
   | *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. | false | boolean
   | *projectId* (producer) | *Required* Cloud project ID |  | String
   | *region* (producer) | *Required* FunctionGraph service region. This is lower precedence than endpoint based configuration |  | String
  
positive.code: [source,xml]
  ----
  <dependency>
      <groupId>org.apache.camel</groupId>git
      <artifactId>camel-huaweicloud-functiongraph</artifactId>
      <version>x.x.x</version>
      <!-- use the same version as your Camel core version -->
  
negative.code: 
  == Using ServiceKey Configuration Bean
  
  Authentication key and secret keys are required to authenticate against cloud FunctionGraph service. You can avoid having them being exposed
  and scattered over in your endpoint uri by wrapping them inside a bean of class `org.apache.camel.component.huaweicloud.functiongraph.models.ServiceKeys`.
  Add it to the registry and let Camel look it up by referring the object via endpoint query parameter `serviceKeys`.
  
  