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
SecureSettings in NotificationService
are buggy
#35378
Comments
Pinging @elastic/es-core-infra |
The most easy repro I found for this is:
For pager duty, the only workaround I found was to remove the secure setting from the keystore and use the "old" way of setting it via elasticsearch.yml. |
NotificationService
implementations (egSlackService
,PagerDutyService
, ..) are buggy.They fail the communication service if the
secure_*
variant of the settings are put in the cluster state as opposed to inside the keystore, as documented https://www.elastic.co/guide/en/elastic-stack-overview/6.3/actions-pagerduty.html#configuring-pagerduty (for eg).The normal behavior should be to simply ignore the setting when in the cluster state. In this case the service would fail to start and complain that the setting is not found in the keystore.
The text was updated successfully, but these errors were encountered: