Allow injection of extra arguments into /etc/elasticsearch/elasticsearch.yml

Bug #1864796 reported by Paul Goins
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Elasticsearch Charm
Expired
Wishlist
Unassigned

Bug Description

It may be desirable to allow for injection of arbitrary arguments into /etc/elasticsearch/elasticsearch.yml.

One use case is to work around pad.lv/1864794, as we could effectively put ES 7.0 into development mode by injecting the setting "discovery.type: single-node". (Without this or without proper bootstrap configuration, ES 7.0+ does not presently work with this charm.)

Revision history for this message
Xav Paice (xavpaice) wrote :

Is there a use case for this beyond adding ES 7 to the charm? Ideally, this kind of config option is used to get past the temporary need for additions to the charm, in this case support for a later release of the product, but the rule of thumb would be that if we need to use the config option, we should be raising a bug against the charm for it to do the right thing already.

Changed in charm-elasticsearch:
status: New → Incomplete
Changed in charm-elasticsearch:
importance: Undecided → Low
importance: Low → Wishlist
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Elasticsearch Charm because there has been no activity for 60 days.]

Changed in charm-elasticsearch:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.