-
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
[Reporting] Update some runtime validations #53975
[Reporting] Update some runtime validations #53975
Conversation
Pinging @elastic/kibana-reporting-services (Team:Reporting Services) |
This PR would be a good time to add string tags for translation in this validation files |
78dca6a
to
7bf9f8b
Compare
const reportingKibanaHostName = config.get(configKey); | ||
|
||
if (!reportingKibanaHostName && serverHost === '0') { | ||
// @ts-ignore: No set() method on KibanaConfig, just get() and has() |
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.
This is brought up as a concern in the Reporting migration issue: #53898
ready for review |
x-pack/legacy/plugins/reporting/server/lib/validate/validate_encryption_key.ts
Show resolved
Hide resolved
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.
Just a small note on potential breakages in 7.6.0 with the new validation. Reporting might not work, but I'd hate for us to prevent kibana from starting due to breaking config change.
💚 Build SucceededHistory
To update your PR or re-run it, just comment with: |
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
* [Reporting] Update some runtime validations * fix unit test * i18n * make warning logging of encryptionKey possible * update snapshot * revert unrelated config change
Summary
Release note: added a self-check for Reporting to prevent an incompatible config from stopping Reporting from working.
server.host: "0"
Checklist
Use
strikethroughsto remove checklist items you don't feel are applicable to this PR.[ ] This was checked for cross-browser compatibility, including a check against IE11[ ] This was checked for keyboard-only and screenreader accessibility