Migrate Keystore to New Platform #52107
Assignees
Labels
blocker
Feature:Configuration
Settings in kibana.yml
Feature:NP Migration
Team:Operations
Team label for Operations Team
v8.0.0
Comments
tylersmalley
added
blocker
Team:Operations
|
Pinging @elastic/kibana-operations (Team:Operations) |
|
This seems wrong, but the only usages I find are in CLI tools. I'm not familiar with what we use the keystore for in Kibana, are there plugins using this API? If not, could we not move this to somewhere in |
jbudz
added a commit
to jbudz/kibana
that referenced
this issue
Nov 16, 2020
Currently keystore parsing is in the legacy http server folder. Keystore references end in src/cli so instead of migrating to core/server the I opted for the closest fit in the CLI folder. Closes elastic#52107
jbudz
added a commit
that referenced
this issue
Nov 17, 2020
Currently keystore parsing is in the legacy http server folder. Keystore references end in src/cli so instead of migrating to core/server the I opted for the closest fit in the CLI folder. Closes #52107
jbudz
added a commit
that referenced
this issue
Nov 17, 2020
Currently keystore parsing is in the legacy http server folder. Keystore references end in src/cli so instead of migrating to core/server the I opted for the closest fit in the CLI folder. Closes #52107
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The keystore settings either need exposed by a new plugin in the new platform, or added to core. Currently, these settings are being injected into the Hapi.
The libraries for this are located at https://github.com/elastic/kibana/tree/master/src/legacy/server/keystore
@joshdover do you have a preference for if this should be a new plugin or exposed vai core?
utils/{question,prompt}The text was updated successfully, but these errors were encountered: