-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[keystore] use get_keystore in server cli #72954
Conversation
Pinging @elastic/kibana-operations (Team:Operations) |
@@ -34,7 +34,7 @@ node scripts/functional_tests --assert-none-excluded \ | |||
if [[ -z "$CODE_COVERAGE" ]] ; then | |||
echo " -> building and extracting default Kibana distributable for use in functional tests" | |||
cd "$KIBANA_DIR" | |||
node scripts/build --debug --no-oss | |||
node scripts/build --debug --no-oss --all-platforms |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not clear what this change does. What platform(s) were we not building that we are now? And are we testing those other platforms somehow?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it's a convenience asking ci to do a build for docker that will be reverted before merging - you'll see it on the upload report in jenkins. i'm planning on doing one more pass with that in your exact setup once the uploads are up
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM - I didn't pull the PR for testing but will verify the fix in the next snapshot build.
Looks good to me after |
💚 Build SucceededBuild metrics
History
To update your PR or re-run it, just comment with: |
* [keystore] use get_keystore in server cli * temporily add docker build so this can be retested in original env * Revert "temporily add docker build so this can be retested in original env" This reverts commit 25f401a.
* [keystore] use get_keystore in server cli * temporily add docker build so this can be retested in original env * Revert "temporily add docker build so this can be retested in original env" This reverts commit 25f401a.
* master: (35 commits) Migrated karma tests to jest (elastic#72649) Migrate status page app to core (elastic#72017) Failing test: Jest Tests.src/plugins/vis_type_vega/public (elastic#71834) Fix Firefox TSVB flaky test with switch index patterns (elastic#72882) [ML] Fixing link to index management from file data visualizer (elastic#72863) test: 💍 add test for sub-expression variables (elastic#71644) fix bug (elastic#72809) [keystore] use get_keystore in server cli (elastic#72954) Show step number instead of incomplete step. (elastic#72866) Fix bug where user can't add an exception when "close alert" is checked (elastic#72919) [Monitoring] Fix issues displaying alerts (elastic#72891) [Ingest Manager] Add more Fleet concurrency tests elastic#71744 (elastic#72338) [Security Solution][Exceptions] - Update UI exceptions builder nested logic (elastic#72490) disable renovate masterIssue [ML] API integration tests for UPDATE data frame analytics endpoint (elastic#72710) [Uptime] Fix accessibility issue in Uptime app nav links (elastic#72926) [Maps] fix removing global filter from layer can cause app to start thrashing (elastic#72763) [Maps] fix blended layer aggregation error when using composite aggregation (elastic#72759) fix unexpected arguments to unload command Limits the upload size of lists to 9 meg size (elastic#72898) ...
A new helper util to get the correct keystore path was introduced during the deprecation of data/kibana.keystore. This was not used the the sibling cli read_keystore and was causing scenarios with writes to the config folder and reads from the data folder.
This was initially found in docker images but is not docker specific
Closes #72323
manual testing
rm -f {data,config}/kibana.keystore
before fix
the server inconrrectly reads from the data directory and starts when it should not
after fix
examples uses an invalid config value with an expected exit error on start
data path
config path