New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[management-api] Normalize Elasticsearch configuration #212

Closed
brasseld opened this Issue Sep 6, 2016 · 1 comment

Comments

Projects
None yet
2 participants
@brasseld
Member

brasseld commented Sep 6, 2016

The way to configure Elasticsearch is not the same between the gateway and the management-rest-api. It would be really great to keep an homogeneous configuration.

Gateway:

  elasticsearch:
    enabled: true # Is the reporter enabled or not (default to true)
    hosts:
      - ${ds.elastic.host}:${ds.elastic.port}
    cluster: gravitee
    index: gravitee
    bulk:
      actions: 1000           # Number of requests action before flush
      flush_interval: 5       # Flush interval in seconds
      concurrent_requests: 5  # Concurrent requests

Management API:

  elasticsearch:
    hosts:
      - ${ds.elastic.host}:${ds.elastic.port}
    index:
      name: gravitee
    cluster:
      name: gravitee
@brasseld

This comment has been minimized.

Member

brasseld commented Sep 6, 2016

Please note that this issue has an impact on configuration (gravitee.yml) for previous version (management-rest-api).

@brasseld brasseld added this to the 0.19.0 milestone Sep 6, 2016

tcompiegne added a commit to gravitee-io-community/gravitee-repository-elasticsearch that referenced this issue Sep 6, 2016

brasseld added a commit to gravitee-io/gravitee-management-rest-api that referenced this issue Sep 6, 2016

tcompiegne added a commit to gravitee-io/gravitee-management-rest-api that referenced this issue Sep 6, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment