src/main/resources/Documentation/Config.md

Configuration
=========================

The events-aws-kinesis plugin is configured by adding a plugin stanza in the
`gerrit.config` file, for example:

```text
[plugin "events-aws-kinesis"]
    numberOfSubscribers = 6
    pollingIntervalMs = 500
    maxRecords = 99
    region = us-east-1
    endpoint = http://localhost:4566
    applicationName = instance-1
    initialPosition = trim_horizon
```

`plugin.events-aws-kinesis.numberOfSubscribers`
:   Optional. The number of expected kinesis subscribers. This will be used to allocate
    a thread pool able to run all subscribers.
    Default: 6

`plugin.events-aws-kinesis.pollingIntervalMs`
:   Optional. How often, in milliseconds, to poll Kinesis shards to retrieve
    records. Please note that setting this value too low might incur in
    `ProvisionedThroughputExceededException`.
    See [AWS docs](https://docs.aws.amazon.com/streams/latest/dev/kinesis-low-latency.html)
    for more details on this.
    Default: 1000

`plugin.events-aws-kinesis.maxRecords`
:   Optional. The maximum number of records to fetch from the kinesis stream
    Default: 100

`plugin.events-aws-kinesis.region`
:   Optional. Which AWS region to connect to.
    Default: When not specified this value is provided via the default Region
    Provider Chain, as explained [here](https://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/credentials.html)

`plugin.events-aws-kinesis.endpoint`
:   Optional. When defined, it will override the default kinesis endpoint and it
    will connect to it, rather than connecting to AWS. This is useful when
    developing or testing, in order to connect locally.
    See [localstack](https://github.com/localstack/localstack) to understand
    more about how run kinesis stack outside AWS.
    Default: <empty>

`plugin.events-aws-kinesis.applicationName`
:   Optional. This value identifies the application and it must be unique within your
    gerrit cluster to allow different gerrit nodes to have different checkpoints
    and to consume data from the stream independently.
    Default: events-aws-kinesis

`plugin.events-aws-kinesis.initialPosition`
:   Optional. Which point in the stream the consumer should start consuming from.
    Note that this only applies to consumers that *do not* have any persisted
    checkpoint (i.e. first deployments). When checkpoints exist they always
    override this value.

    Needs to be one of these values:

* TRIM_HORIZON: Start streaming at the last untrimmed record in the shard, which is the oldest data record in the shard.
* LATEST: Start streaming just after the most recent record in the shard, so that you always read the most recent data in the shard.

    Default: "LATEST"

`plugin.events-aws-kinesis.publishSingleRequestTimeoutMs`
: Optional. The maximum total time (milliseconds) elapsed between when a publish
  request started and the receiving a response. If it goes over, the request
  will be timed-out and possibly tried again, if `publishTimeoutMs` allows.
  Default: 6000

`plugin.events-aws-kinesis.publishTimeoutMs`
: Optional. The maximum total time (milliseconds) waiting for publishing a record
  to kinesis, including retries.
  If it goes over, the request will be timed-out and not attempted again.
  Default: 6000

`plugin.events-aws-kinesis.shutdownTimeoutMs`
: Optional. The maximum total time (milliseconds) waiting when shutting down
  kinesis consumers.
  Default: 20000

`plugin.events-aws-kinesis.awsLibLogLevel`
: Optional. Which level AWS libraries should log at.
  This plugin delegates most complex tasks associated to the production and
  consumption of data to libraries developed and maintained directly by AWS.
  This configuration specifies how verbose those libraries are allowed to be when
  logging.

  Default: WARN
  Allowed values:OFF|FATAL|ERROR|WARN|INFO|DEBUG|TRACE|ALL

`plugin.events-aws-kinesis.streamEventsTopic`
:   Optional. Name of the kinesis topic for stream events. events-aws-kinesis
    plugin exposes all stream events under this topic name.
    Default: gerrit

`plugin.events-aws-kinesis.sendAsync`
:   Optional. Whether to send messages to Kinesis asynchronously, without
    waiting for the result of the operation.
    Note that in this case, retries will still be attempted by the producer, but
    in a separate thread, so that Gerrit will not be blocked waiting for the
    publishing to terminate.
    The overall result of the operation, once available, will be logged.
    Default: true

Overrides
=========================

Note that System properties always override and take priority over the above
gerrit.config configuration.