We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The reload-secure-store-action feature branch adds support for a reloadable keystore.
Watcher uses keystore settings for Slack, Hipchat, PagerDuty, Jira.
While at it, the Email service should also get a new secure setting for the user/password of a user.
Lastly, we should align the deprecation with of the non secure settings, how it is done with the other discovery/plugin settings.
The text was updated successfully, but these errors were encountered:
Pinging @elastic/es-core-infra
Sorry, something went wrong.
This one seems obsolete. AFAICT, Watcher can now reload secure settings as part of its notification service (#31746)?
This is obsolete, as keystore settings can now be reloaded.
hub-cap
No branches or pull requests
The reload-secure-store-action feature branch adds support for a reloadable keystore.
Watcher uses keystore settings for Slack, Hipchat, PagerDuty, Jira.
While at it, the Email service should also get a new secure setting for the user/password of a user.
Lastly, we should align the deprecation with of the non secure settings, how it is done with the other discovery/plugin settings.
The text was updated successfully, but these errors were encountered: