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

Create keystore on RPM and Debian package install #26282

Merged
merged 1 commit into from Aug 18, 2017

Conversation

Projects
None yet
4 participants
@jasontedor
Copy link
Member

commented Aug 18, 2017

When Elasticsearch starts up, it tries to create a keystore if one does not exist; this is so the keystore can be seeded. With the RPM and Debian packages, the keystore would be located in /etc/elasticsearch. This configuration directory is typically not writable by the elasticsearch user so the Elasticsearch process will not have permission to create the keystore. Instead, the RPM and Debian packages should create the keystore (if it does not exist) on package installation. This commit enables these packages to do that in the post-install routines.

Create keystore on RPM and Debian package install
When Elasticsearch starts up, it tries to create a keystore if one does
not exist; this is so the keystore can be seeded. With the RPM and
Debian packages, the keystore would be located in
/etc/elasticsearch. This configuration directory is typically not
writable by the elasticsearch user so the Elasticsearch process will not
have permission to create the keystore. Instead, the RPM and Debian
packages should create the keystore (if it does not exist) on package
installation. This commit enables these packages to do that in the
post-install routines.
@s1monw

s1monw approved these changes Aug 18, 2017

Copy link
Contributor

left a comment

LGTM thanks so much

@jasontedor jasontedor merged commit a894f89 into elastic:master Aug 18, 2017

1 of 2 checks passed

elasticsearch-ci Build started sha1 is merged.
Details
CLA Commit author is a member of Elasticsearch
Details

jasontedor added a commit that referenced this pull request Aug 18, 2017

Create keystore on RPM and Debian package install
When Elasticsearch starts up, it tries to create a keystore if one does
not exist; this is so the keystore can be seeded. With the RPM and
Debian packages, the keystore would be located in
/etc/elasticsearch. This configuration directory is typically not
writable by the elasticsearch user so the Elasticsearch process will not
have permission to create the keystore. Instead, the RPM and Debian
packages should create the keystore (if it does not exist) on package
installation. This commit enables these packages to do that in the
post-install routines.

Relates #26282

jasontedor added a commit that referenced this pull request Aug 18, 2017

Create keystore on RPM and Debian package install
When Elasticsearch starts up, it tries to create a keystore if one does
not exist; this is so the keystore can be seeded. With the RPM and
Debian packages, the keystore would be located in
/etc/elasticsearch. This configuration directory is typically not
writable by the elasticsearch user so the Elasticsearch process will not
have permission to create the keystore. Instead, the RPM and Debian
packages should create the keystore (if it does not exist) on package
installation. This commit enables these packages to do that in the
post-install routines.

Relates #26282

@jasontedor jasontedor deleted the jasontedor:rpm-deb-create-keystore branch Aug 18, 2017

@lcawl lcawl removed the v6.1.0 label Dec 12, 2017

@colings86 colings86 added v7.0.0-beta1 and removed v7.0.0 labels Feb 7, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.