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 optimize into data folder #25944

Merged
merged 25 commits into from
Aug 28, 2019
Merged

move optimize into data folder #25944

merged 25 commits into from
Aug 28, 2019

Conversation

jbudz
Copy link
Member

@jbudz jbudz commented Nov 20, 2018

We have a general purpose data folder used for application writes, and there's some overlap with this and the optimize folder. We want all writes to go to the same folder so we can set this path to /var/lib/kibana for deb/rpm packages.

https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch05s08.html

This hierarchy holds state information pertaining to an application or the system. State information is data that programs modify while they run, and that pertains to one specific host. Users must never need to modify files in /var/lib to configure a package's operation, and the specific file hierarchy used to store the data must not be exposed to regular users.

Currently in the data folder we'll extract phantomjs, create a uuid, and store the keystore. This moves bundles and bundle caches there in addition

Closes #15899
Closes #5071

@jbudz jbudz added review Team:Operations Team label for Operations Team labels Nov 20, 2018
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-operations

@tylersmalley
Copy link
Contributor

Do we have any public documentation mentioning the previous location?

@mistic
Copy link
Member

mistic commented Nov 20, 2018

@jbudz I have to little questions. Should we also update src/dev/notice/generate_notice_from_source.js ? I like that idea as it will help us to prevent unintended deletion of that folder, but shouldn't we create a way to let users know that we move that folder?

@elasticmachine

This comment has been minimized.

@elasticmachine

This comment has been minimized.

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

Copy link
Member

@mistic mistic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@elasticmachine
Copy link
Contributor

💔 Build Failed

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

@elasticmachine
Copy link
Contributor

💔 Build Failed

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

@tylersmalley
Copy link
Contributor

nit: can remove /optimize from .eslintignore

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

@jbudz jbudz added the non-issue Indicates to automation that a pull request should not appear in the release notes label Mar 27, 2019
@jbudz jbudz requested a review from a team as a code owner August 9, 2019 18:35
@jbudz
Copy link
Member Author

jbudz commented Aug 9, 2019

Getting this ready again - I wanted to wait to avoid workflow interruptions when switching between 8.x and 7.x but at the same time don't want to wait too long :)

@jbudz jbudz added release_note:skip Skip the PR/issue when compiling release notes and removed non-issue Indicates to automation that a pull request should not appear in the release notes labels Aug 9, 2019
@elasticmachine
Copy link
Contributor

💚 Build Succeeded

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

Copy link
Contributor

@spalger spalger left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

@jbudz jbudz merged commit bad947d into elastic:master Aug 28, 2019
tylersmalley pushed a commit to tylersmalley/kibana that referenced this pull request Sep 24, 2019
We can either remove the legacy optimize directory from gitignore, or we
can add to eslintignore. We have choosen to go with the latter o
prevent accidental commits of the optimize directory and a smoother
transition between old branches. This change was made in elastic#25944 and only
effects master/8.0, which increases the likelyhood a developer runs into
it.

Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
tylersmalley pushed a commit to tylersmalley/kibana that referenced this pull request Sep 24, 2019
We can either remove the legacy optimize directory from gitignore, or we can add to eslintignore. We have chosen to go with the latter to prevent accidental commits of the optimize directory and aide in a smoother transition between old branches. This change was made in elastic#25944 and only effects master/8.0, which increases the likelihood a developer runs into it.

Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
tylersmalley pushed a commit that referenced this pull request Sep 24, 2019
We can either remove the legacy optimize directory from gitignore, or we can add to eslintignore. We have chosen to go with the latter to prevent accidental commits of the optimize directory and aide in a smoother transition between old branches. This change was made in #25944 and only effects master/8.0, which increases the likelihood a developer runs into it.

Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release_note:skip Skip the PR/issue when compiling release notes review Team:Operations Team label for Operations Team v8.0.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

OS packages should not write to /usr/share/kibana Customizable optimize directory
6 participants