{
	"connector": {
		"class": "org.apache.camel.kafkaconnector.yammer.CamelYammerSinkConnector",
		"artifactId": "camel-yammer-kafka-connector",
		"groupId": "org.apache.camel.kafkaconnector",
		"id": "camel-yammer-sink",
		"type": "sink",
		"version": "0.7.3-SNAPSHOT",
		"description": "Interact with the Yammer enterprise social network."
	},
	"properties": {
		"camel.sink.path.function": {
			"name": "camel.sink.path.function",
			"description": "The function to use One of: [MESSAGES] [MY_FEED] [ALGO] [FOLLOWING] [SENT] [PRIVATE] [RECEIVED] [USERS] [CURRENT]",
			"priority": "HIGH",
			"required": "true",
			"enum": [
				"MESSAGES",
				"MY_FEED",
				"ALGO",
				"FOLLOWING",
				"SENT",
				"PRIVATE",
				"RECEIVED",
				"USERS",
				"CURRENT"
			]
		},
		"camel.sink.endpoint.useJson": {
			"name": "camel.sink.endpoint.useJson",
			"description": "Set to true if you want to use raw JSON rather than converting to POJOs.",
			"defaultValue": "false",
			"priority": "MEDIUM",
			"required": "false"
		},
		"camel.sink.endpoint.lazyStartProducer": {
			"name": "camel.sink.endpoint.lazyStartProducer",
			"description": "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.",
			"defaultValue": "false",
			"priority": "MEDIUM",
			"required": "false"
		},
		"camel.sink.endpoint.requestor": {
			"name": "camel.sink.endpoint.requestor",
			"description": "To use a specific requester to communicate with Yammer.",
			"priority": "MEDIUM",
			"required": "false"
		},
		"camel.sink.endpoint.synchronous": {
			"name": "camel.sink.endpoint.synchronous",
			"description": "Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported).",
			"defaultValue": "false",
			"priority": "MEDIUM",
			"required": "false"
		},
		"camel.sink.endpoint.accessToken": {
			"name": "camel.sink.endpoint.accessToken",
			"description": "The access token",
			"priority": "HIGH",
			"required": "true"
		},
		"camel.sink.endpoint.consumerKey": {
			"name": "camel.sink.endpoint.consumerKey",
			"description": "The consumer key",
			"priority": "HIGH",
			"required": "true"
		},
		"camel.sink.endpoint.consumerSecret": {
			"name": "camel.sink.endpoint.consumerSecret",
			"description": "The consumer secret",
			"priority": "HIGH",
			"required": "true"
		},
		"camel.component.yammer.useJson": {
			"name": "camel.component.yammer.useJson",
			"description": "Set to true if you want to use raw JSON rather than converting to POJOs.",
			"defaultValue": "false",
			"priority": "MEDIUM",
			"required": "false"
		},
		"camel.component.yammer.lazyStartProducer": {
			"name": "camel.component.yammer.lazyStartProducer",
			"description": "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.",
			"defaultValue": "false",
			"priority": "MEDIUM",
			"required": "false"
		},
		"camel.component.yammer.autowiredEnabled": {
			"name": "camel.component.yammer.autowiredEnabled",
			"description": "Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.",
			"defaultValue": "true",
			"priority": "MEDIUM",
			"required": "false"
		},
		"camel.component.yammer.configuration": {
			"name": "camel.component.yammer.configuration",
			"description": "Component configuration",
			"priority": "MEDIUM",
			"required": "false"
		},
		"camel.component.yammer.requestor": {
			"name": "camel.component.yammer.requestor",
			"description": "To use a specific requester to communicate with Yammer.",
			"priority": "MEDIUM",
			"required": "false"
		},
		"camel.component.yammer.accessToken": {
			"name": "camel.component.yammer.accessToken",
			"description": "The access token",
			"priority": "HIGH",
			"required": "true"
		},
		"camel.component.yammer.consumerKey": {
			"name": "camel.component.yammer.consumerKey",
			"description": "The consumer key",
			"priority": "HIGH",
			"required": "true"
		},
		"camel.component.yammer.consumerSecret": {
			"name": "camel.component.yammer.consumerSecret",
			"description": "The consumer secret",
			"priority": "HIGH",
			"required": "true"
		}
	}
}