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

Move kibana.keystore to the configuration directory #25746

Closed
inqueue opened this issue Nov 15, 2018 · 4 comments · Fixed by #57856
Closed

Move kibana.keystore to the configuration directory #25746

inqueue opened this issue Nov 15, 2018 · 4 comments · Fixed by #57856
Assignees
Labels
enhancement New value added to drive a business result Team:Operations Team label for Operations Team

Comments

@inqueue
Copy link
Member

inqueue commented Nov 15, 2018

Describe the feature:
kibana.keystore resides in data for tar/zip installations and /var/lib/kibana for package installations. Move kibana.keystore to config for tar/zip installations and /etc/kibana for package installations. It would be a breaking change for existing installations using kibana.keystore.

Describe a specific use case for the feature:
This would make the keystore location consistent with Elasticsearch.

@inqueue inqueue added Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more! enhancement New value added to drive a business result labels Nov 15, 2018
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-security

@kobelb
Copy link
Contributor

kobelb commented Nov 15, 2018

/cc @elastic/kibana-operations since this is technically dealing with the distro packages it seems more inline with operations responsibilities, do you agree?

@jbudz jbudz added Team:Operations Team label for Operations Team and removed Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more! labels Nov 15, 2018
@jbudz
Copy link
Member

jbudz commented Nov 15, 2018

👍 We need to add a path.conf config and replace all the static, sync checks in server/path. A precursor to that is to make the global config available standalone.

@tylersmalley tylersmalley changed the title move kibana.keystore to the configuration directory Move kibana.keystore to the configuration directory Feb 11, 2019
jbudz added a commit to jbudz/kibana that referenced this issue Feb 18, 2020
This is a breaking change to move the location of kibana-keystore.
Keystores in other stack products live in the config directory, so this
updates our current path to be consistent.

Closes elastic#25746
@tylersmalley
Copy link
Contributor

Move to config directory, fall back to default data directory location to prevent a break in the minor. This fallback should not be present in 8.0.

jbudz added a commit that referenced this issue Jul 13, 2020
* Move kibana-keystore from data/ to config/

This is a breaking change to move the location of kibana-keystore.
Keystores in other stack products live in the config directory, so this
updates our current path to be consistent.

Closes #25746

* add breaking changes

* update comment

* wip

* fix docs

* read from both keystore locations, write priority to non-deprecated

* note data directory fallback

* add tests for get_keystore

Co-authored-by: Elastic Machine <[email protected]>
jbudz added a commit that referenced this issue Jul 13, 2020
* Move kibana-keystore from data/ to config/

This is a breaking change to move the location of kibana-keystore.
Keystores in other stack products live in the config directory, so this
updates our current path to be consistent.

Closes #25746

* add breaking changes

* update comment

* wip

* fix docs

* read from both keystore locations, write priority to non-deprecated

* note data directory fallback

* add tests for get_keystore

Co-authored-by: Elastic Machine <[email protected]>
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 Team:Operations Team label for Operations Team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants