Skip to content
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

Support dynamically setting headers via kibana.yml or REST api #19829

Closed
zanbel opened this issue Jun 12, 2018 · 0 comments
Closed

Support dynamically setting headers via kibana.yml or REST api #19829

zanbel opened this issue Jun 12, 2018 · 0 comments
Labels
enhancement New value added to drive a business result stale Used to mark issues that were closed for being stale Team:Cloud Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc Team:Operations Team label for Operations Team

Comments

@zanbel
Copy link

zanbel commented Jun 12, 2018

Describe the feature:
Currently any change to attributes in kibana.yml requires a restart to the service in order for the change to take affect.
We would like to be able to use a REST API, or be able to dynamically load the config file when it changes without having to restart.

Describe a specific use case for the feature:
Specifically we are planning to use the headers to pass an authentication token and wanted to be able to use short living token that will be refreshed every X minutes. Even if going with a longer term tokens there is also might be a need to revoke the token and insert a new one.
Currently to support this behaviour we will need to restart kibana service very often.

// cc @alexfrancoeur @paulplace @swallez @nkvoll @igor-kupczynski

@bhavyarm bhavyarm added Team:Operations Team label for Operations Team triage_needed Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc labels Jun 19, 2018
@jbudz jbudz added enhancement New value added to drive a business result and removed triage_needed labels Jun 25, 2018
@joshdover joshdover added the stale Used to mark issues that were closed for being stale label Jan 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New value added to drive a business result stale Used to mark issues that were closed for being stale Team:Cloud Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc Team:Operations Team label for Operations Team
Projects
None yet
Development

No branches or pull requests

4 participants